I Read It But Don’t Get It, or How to Tackle Technical Texts
summary
Claim: readers who make thinking visible learn technical books faster by using three focus questions and tracking notes. Concrete tools are index card + sticky flags + pen to tag connections, questions, summaries and important lines. Practice: preview chapters, connect to code, question claims, review and try to apply. Result: mental engagement rises, confusion drops, interest increases; immediate refactor changes rarely appear and applying ideas to a codebase takes repeated encounters rather than a single read.
AI-written summary · about
chapters (7)
- 0:00Start
- 7:35Baseline Assumptions
- 8:50Texts Are Not Documents Set in Stone
- 9:40What Is an Engaged Reader Doing
- 16:24Identify Important Ideas
- 26:58Note the Silence
- 27:59Be Patient
