Honest Take — Before You Begin
The thirty-day self-test is where the abstract claim "engineered retention beats unengineered retention" turns into a number with your name attached, and I want you to run it befo…
Operationalize the two highest-evidence learning methods — retrieval practice and spaced repetition — inside your teaching artifacts, and internalize the reframe: retention is not the learner's responsibility; it is the teacher's design responsibility. Retention engineering is cache-invalidation discipline. The forgetting curve specifies the TTL; spaced repetition is scheduled refresh; retrieval practice is the read that catches stale data before it causes a downstream failure. "Review this on your own time" is the teaching equivalent of "the user will manually clear their cache" — a sentence you would never let into a design doc. Engineers who can reason about cache invalidation can absolutely reason about memory invalidation; the discipline is simply to accept that the cache is your responsibility, because you wrote to it.
This course unlocks once you've finished its prerequisite. Open prerequisite →
The thirty-day self-test is where the abstract claim "engineered retention beats unengineered retention" turns into a number with your name attached, and I want you to run it befo…
Forgetting is the default state of the human brain. Without engineered retention, learners forget 50-90% of content within weeks — the Ebbinghaus forgetting curve, robustly replic…
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
1. Build a retention layer for one real artifact (a module of a course you run, a long-form guide, your package's concepts): 15-30 retrieval prompts covering the load-bearing conc…
7 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.