I keep a pad of paper next to me. Though I do nearly everything on the computer, I use paper to write down anything I need to look up later. The list isn't fo

I keep a pad of paper next to me. Though I do nearly everything on the computer, I use paper to write down anything I need to look up later. The list isn't for things I need to learn, but for how to do something I need to know how to do on a regular basis. If I were studying math, and I knew how to use a theorem but didn't understand how it worked, I might write that down. The point of the pad is to keep on task and only take a brief note. For any programming language there are two other things I do. First, I make a repo with a bunch of nested directories that I'll add to. So I'll have something like Array -> Iteration, and that might contain 5 different programs going through different types of iteration. Yes, a book will have that, but actually coding it really helps it sink in. The first place I look for resources (even before something like <language>.com) is stackoverflow. Search for the tag of the language (like "[go]"), then click "Learn more...". I've found these lists of resources to be the best jumping off point, though the language may vary. Again I use the pad for details of the language. There are times when I know I'm doing something that works but is maybe slow or looks ugly because the language has facilities to do it more cleanly. Then there are the personal differences. I've reached a decent level of fluency in 2 other languages. I really struggled early on with typical instruction until I tailored study to my style of learning. Where most people seem to learn new words through use and context, I did so much better by learning them on paper -- to the point where it was a substantial departure from the rest of the class. So my point here is to figure out what works and don't be afraid to do things differently.