the short answer is "yes". Whenever I finish a task, I set out to write 5 flashcards on the most surprising or interesting facts that I had to learn in order to complete it. Often, I look at the DMs I've exchanged with some teammate, and pick up a few gems here and there.
The key here is not to get overwhelmed by it. The process should be guiding what you need to learn, not the other way around. Which means that it is OK if you don't capture everything on the first pass—if that part of the codebase is important, you'll be looking at it very soon.
Interesting method, thank you! Working in a larger organisation, I often forget nuggets of knowledge, especially those that sprout from the interactions between different domains (be it implementation decisions, processes, general domain knowledge...). Perhaps it's a use-case to try this on!
Great insights, thank you!
I've used spaced repetition extensively for things like languages / exams. I'm curious about how one goes about using flashcards for things like
> Large codebases where I needed to hit the ground running
Is it just mini facts that you discover while reading the codebase? Could you give some example?
Hi Eleni,
the short answer is "yes". Whenever I finish a task, I set out to write 5 flashcards on the most surprising or interesting facts that I had to learn in order to complete it. Often, I look at the DMs I've exchanged with some teammate, and pick up a few gems here and there.
The key here is not to get overwhelmed by it. The process should be guiding what you need to learn, not the other way around. Which means that it is OK if you don't capture everything on the first pass—if that part of the codebase is important, you'll be looking at it very soon.
Interesting method, thank you! Working in a larger organisation, I often forget nuggets of knowledge, especially those that sprout from the interactions between different domains (be it implementation decisions, processes, general domain knowledge...). Perhaps it's a use-case to try this on!