[[Anki]] gives you a tight [[Feedback loop]] for reading technical books. My method for creating Anki cards is simple. I usually quote a paragraph from a book or other source and add a plain text question right below. This avoids context switching. The cognitive load is deferred. Old me might think this is ineffective, but new me thinks [[Perfect is the enemy of good]]. Perfection rarely takes [[The Magical Number Seven, Plus or Minus Two]] or other psychological factors into account. This workflow is deliberately designed to conserve mental energy. It's inspired by [[Andy Matuschak]] [method](https://youtu.be/kG2_6ToMZgI?t=2007). For example, from [[Let's Go (book notes)]]: > The second component is a router (or servemux in Go terminology). This stores a mapping between the URL patterns for your application and the corresponding handlers. Usually you have one servemux for your application containing all your routes. Q: In Go, what stores a mapping between the URL patterns and the corresponding handlers? #anki/added A: A servemux (router).