references/study_method_canon.md
Studying a Hard Technical Text
This book defeats more readers than it teaches, and the reason is rarely ability. It is a reference text with textbook page counts, high element interactivity, and no exercises. The methods below are the evidence-based ones that apply specifically to that shape of material.
The five that matter here
1. Retrieval practice beats re-reading
Testing yourself on material produces markedly better long-term retention than reviewing it, even when re-reading feels more productive at the time (Roediger & Karpicke, 2006). For this book, the cheap version: after each chapter, close it and write the chapter's core idea, three concepts, and one thing you could not explain. The chapter files in this skill are structured to be checked against, not read first — use them as the answer key.
2. Spacing beats massing
Distributed practice outperforms cramming for durable retention (Cepeda et al., 2006). Practical rule: revisit ch05 and ch11 at one week and one month. They are the chapters whose vocabulary every later chapter reuses, so spaced review of those two pays across the whole book.
3. Worked examples before problem-solving, for novices
For learners without domain schemas, studying worked examples is more effective than solving equivalent problems — the expertise-reversal effect means this flips once you have the schemas (Sweller & Cooper, 1985; Kalyuga et al., 2003). Consequence for this book: in Ch 8 and Ch 18, work the derivations the text presents before attempting your own; in Ch 11, do the opposite — you already have the schema, so run the workflow on a real project.
4. Self-explanation
Students who explain each step to themselves while studying examples learn substantially more than those who do not (Chi et al., 1989). The highest-yield prompt for this book: after every equation, answer "what would change if this term were removed?" It converts symbol-tracking into understanding, and it is exactly how the book's own arguments are structured.
5. Desirable difficulties
Conditions that slow acquisition often improve retention and transfer (Bjork & Bjork, 2011). Interleaving Part II chapters with attempts to apply them beats reading Part II straight through, even though it feels slower. This is the empirical case for the reading-path planner's "read one chapter, then implement something" cadence.
Managing cognitive load in Chapters 2–4 and 16–20
High element interactivity — where symbols cannot be understood one at a time because they only make sense in relation to each other — is what makes these chapters expensive (Sweller, van Merriënboer & Paas, 1998). Intrinsic load cannot be reduced by better presentation; it can only be sequenced. Two consequences:
- Do not skim a high-interactivity derivation. Skimming works for prose and fails for Chapter 18. Either work it or defer it explicitly.
- Chunk by named object. "Score matching" as one unit is cheaper than seven equations. Every chapter file in this skill names its objects for exactly this reason.
A cadence that works for this book
- Skim the chapter's section headings and the summary. Five minutes.
- Read with a pen, working every derivation you intend to keep.
- Close the book and write, from memory: the core idea, three concepts, one confusion.
- Check against this skill's chapter file — it is deliberately written as a synthesis, so a mismatch is informative.
- Apply something small before moving on (a five-line implementation, a diagnosis of a real training run, a re-derivation).
- Revisit at one week for ch05, ch08, ch11, ch18.
Step 5 is the one most readers skip and the one that decides whether any of it survives.
What not to do
- Reading front-to-back through Part I as a first pass. See
prerequisite_map.md. - Highlighting. It produces a strong feeling of learning and among the weakest measured effects of the common study techniques (Dunlosky et al., 2013).
- Taking notes that restate the text. Restatement is transcription. Write the answer to "when would I use this?" instead — that is the note that gets read again.
- Waiting to "finish the math" before touching a model. The book's own Ch 11 argues against it: build the end-to-end pipeline early.
Sources
- Roediger & Karpicke, "Test-Enhanced Learning: Taking Memory Tests Improves Long-Term Retention," Psychological Science 17(3), 2006.
- Cepeda, Pashler, Vul, Wixted & Rohrer, "Distributed Practice in Verbal Recall Tasks: A Review and Quantitative Synthesis," Psychological Bulletin 132(3), 2006.
- Sweller & Cooper, "The Use of Worked Examples as a Substitute for Problem Solving in Learning Algebra," Cognition and Instruction 2(1), 1985; Kalyuga, Ayres, Chandler & Sweller, "The Expertise Reversal Effect," Educational Psychologist 38(1), 2003.
- Chi, Bassok, Lewis, Reimann & Glaser, "Self-Explanations," Cognitive Science 13(2), 1989.
- Bjork & Bjork, "Making Things Hard on Yourself, But in a Good Way," in Psychology and the Real World, 2011.
- Sweller, van Merriënboer & Paas, "Cognitive Architecture and Instructional Design," Educational Psychology Review 10(3), 1998.
- Dunlosky, Rawson, Marsh, Nathan & Willingham, "Improving Students' Learning With Effective Learning Techniques," Psychological Science in the Public Interest 14(1), 2013.