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.
Is that a flash card thing? I think if you’re actively trying to “retain” knowledge like that you’re probably doing something wrong.
It's a spaced repetition flash card program. If you just want flash cards, you use quizlet.
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.
Understanding is always preferable to pure brute force memorization. For one thing, going through flash cards will be much faster, easier, and less frustrating.
If you don't understand a concept, it's going to create leeches, which suck up study time.
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.
It helps you absorb information and convert it to knowledge, yes. But decay of knowledge is a thing. Flash cards are just the format. What it allows you to do is formulate questions or prompts which allow you to practice active recall. Active recall of information is one of the gold standard for studying.
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.
Simply reading is one of the poorest strategy for learning. Active recall is much better. I agree that implementation and actual practice of skill is a good use of time, which might fall under the category of active recall.
Anyway, I am still trying to find how anki fit in my overall system for learning programming / software engineering. One of the thing I lacked is technical vocabularies for describing what I am seeing or doing, which I think anki can help with a lot.
Some people has success with it, but not for me. I suspect that it has to do something with the low density of cards/notes I added to anki.
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.