18 points by ParallelThread 2 years ago | 5 comments
tra3 2 years ago
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...
leobg 2 years ago
(Obviously it’s been described even earlier, for instance back in the 1960s by BF Skinner, for “programmed instruction“.)
Leftium 2 years ago
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...
minhmeoke 2 years ago
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.
jazzabeanie 2 years ago