| Is that a flash card thing? I think if you’re actively trying to “retain” knowledge like that you’re probably doing something wrong. For context I studied biochemistry in college with the intention of being pre-med and that is how I did all my studying, creating notes and flash cards for rote memorization because memorizing trivia is what’s required to succeed in that path, but I think it’s the wrong approach for furthering your education as a software engineer. I still take notes today sometimes (because the act of writing helps me absorb information), but I’d never go as far as making flash cards. When you’re studying this stuff I think the goal is more like, learn about what’s “out there” so you know enough to recognize that there is a thing whose details you should look up when needed. Let me put it this way, if you read a textbook cover to cover on operating systems you won’t (and don’t need) to remember every little detail of the data structures and algorithms involved. But studying it once means you’ll never forget that they exist or what the difference between a thread and process is, and the remaining details are always a short lookup away when you need them! If you do want to go really deep on a topic than my recommendation would be read about it / study it first, then go implement something in that area (even if it’s just a toy) if you want to make sure you really understand it. |
That said, I still have basically the same opinions you do when it comes to when it comes to using it for most programming skills. Others have a different perspective, though: https://www.semicolonandsons.com/episode/how-to-learn-to-cod...