Creating your own deck is the way to go. Other people's decks never quite clicked for me the same way a self made deck does. A huge part of it is going through the material and identifying the pieces of knowledge that you actually want/need to retain.
Andy Matushchak's prompt guide [0] linked below is amazing. Supermemo's 20 rules for formulating knowledge [1] is great too, Wozniak is the one that invented SRS.
Fluent Forever teaches how to make effective SRS flashcards, based on science and personal experience. I think many of the methods taught by Fluent Forever would work for other domains outside learning foreign languages.
Here are some of the more important points:
- Make your own flashcards (don't just use unmodified decks made by other people). Just the act of making the flashcards exercises your brain so you will be more likely to recall in the future, even if you never use the deck.
- Make personal connections between the facts and yourself. Like if the fact is about `await`, use the first time that keyword helped make your code more readable. What function were you awaiting?
- Connect the facts to visceral feelings/emotions. Perhaps some things are categorized by inconsistent/illogical categories (like German genders). Attach that category to feelings/emotions like hot, cold, explosive, sexy, sad.
- Use images because the brain is better at recalling images than abstract facts.
Andy Matushchak's prompt guide [0] linked below is amazing. Supermemo's 20 rules for formulating knowledge [1] is great too, Wozniak is the one that invented SRS.
[0] https://andymatuschak.org/prompts/
[1] https://www.supermemo.com/en/blog/twenty-rules-of-formulatin...
(Obviously it’s been described even earlier, for instance back in the 1960s by BF Skinner, for “programmed instruction“.)
Here are some of the more important points:
- Make your own flashcards (don't just use unmodified decks made by other people). Just the act of making the flashcards exercises your brain so you will be more likely to recall in the future, even if you never use the deck.
- Make personal connections between the facts and yourself. Like if the fact is about `await`, use the first time that keyword helped make your code more readable. What function were you awaiting?
- Connect the facts to visceral feelings/emotions. Perhaps some things are categorized by inconsistent/illogical categories (like German genders). Attach that category to feelings/emotions like hot, cold, explosive, sexy, sad.
- Use images because the brain is better at recalling images than abstract facts.
https://lifeclub.org/books/fluent-forever-gabriel-wyner-revi...
https://www.grahammann.net/book-notes/fluent-forever-gabriel...
This looks like a nice Anki deck for reviewing system design concepts: https://github.com/donnemartin/system-design-primer
You might also be interested in Alex Xu's System Design Interview Book.