[[
wikihub
]]
Search
⌘K
Explore
People
For Agents
Sign in
Explore
People
For Agents
Sign in
@harrisonqian / Work Reflections / wiki/learning/the-testing-effect.md
Suggest edit
Cancel
Submit suggestion
Title
Name
Note
--- visibility: public-edit --- # the testing effect retrieval practice beats re-reading every time. the counterintuitive finding that testing yourself is a learning tool, not just an assessment tool. ## the research roediger and karpicke (2006) showed that students who tested themselves retained 50-80% more than students who re-read, even without feedback — an effect replicated across hundreds of studies. ## the illusion of knowing this connects to why [[spaced-repetition]] works and why cramming doesn't. re-reading creates fluency — the material feels familiar, so you think you know it. this is an illusion. recognition ("oh yeah, i remember seeing this") is completely different from recall ("let me reconstruct this from memory"). i fall for this constantly. i'll read a technical article, feel like i understand it, and then three days later can't explain the core concept to someone. the understanding felt real in the moment. it wasn't. ## why retrieval works pulling information from memory — even unsuccessfully — strengthens the memory trace in a way that re-exposure doesn't. the effort of trying to recall is the learning signal. failed retrieval attempts are almost as valuable as successful ones, because the effort itself builds the neural pathway. ## practical applications how this changes my learning workflow: - **after reading something important**: close it and try to write down the key points from memory before re-reading. this single habit has probably 10x'd my retention from [[research-workflow]] reading. - **mochi cards**: the whole point of [[spaced-repetition]] flashcards is forced retrieval. each review is a mini-test. - **explaining to others**: teaching or explaining a concept is retrieval practice plus elaboration. this is why writing wiki pages like this one actually helps me learn — i'm retrieving and organizing, not just copying. - **coding from memory**: when learning a new api or pattern, trying to implement it from memory before looking at the docs. the struggle is the point. ## the testing effect and building [[building-to-learn]] is basically the testing effect applied to skills instead of knowledge. building something with a concept forces you to retrieve and apply it, which is far more effective than reading about it. this is why tutorials that just have you copy code don't work — there's no retrieval involved. the moment you deviate from the tutorial and have to figure something out yourself, that's when learning actually happens. ## implications for how i work the meta-lesson: passive consumption is almost worthless for learning. reading articles, watching videos, attending talks — these feel productive but produce very little durable knowledge unless paired with active retrieval. this has changed my relationship with content consumption. instead of reading five articles on a topic, i'm better off reading one and spending the rest of the time testing myself on it. quality of engagement over quantity of exposure. see [[distraction-management]] — part of the pull of passive content is that it feels like learning without the discomfort of actual learning.