"Every perception is to some degree an act of creation, and every act of memory is to some degree an act of imagination."

-- Gerald Edelman, Second Nature: Brain Science and Human Knowledge
Appendix 2: Using Anki to learn APIs2 Appendix 2: Using Anki to learn APIsAppendix 2: Using Anki to learn APIsAugmenting Long-term Memory2020-09-24JournalBut suppose I know I will use the API more seriously in a project. For instance, for my essay Thought as a Technology I wanted to build some prototypes using 3d graphics, and decided to learn the basics of the three.js Javascript library. One tempting failure mode is to think “Oh, I should master the API first”, and then to dive into tutorials or the documentation. Apart from a quick skim of a tutorial or the documentation, that's a mistake. A better approach is to find a small, functioning piece of code that does something related to the core functionality of my project. It doesn't need to be similar to the whole project, but ideally implements one or two similar features, and is a few tens or hundreds of lines of code long. I get that code running, then start making small tweaks, adding bits of functionality I need, taking out bits that I don't, and trying to understand and improve the code.