The Learning System
This curriculum uses 11 recurring learning techniques. They exist to keep the work active, cumulative, and evidence-driven.
The core rule is simple: the guide teaches first, practice makes the concept concrete, and source books are used selectively.
Guide-First Contract
Every module should be usable without reading an entire book front to back.
- Primary path: concept pages, examples, drills, retrieval, and application
- Secondary path: selective source reading labeled
Read only if stuckorOptional deep dive - Default outcome: the learner can explain and use the concept before being asked to consume more prose
The 11 Techniques
1. Spaced Repetition
Review key material on a schedule instead of waiting until you forget everything.
2. Retrieval Practice
Recall the idea before checking notes. Retrieval is part of learning, not just testing.
3. Feynman Notes
Explain the concept in plain language. If you cannot explain it simply, you probably do not understand it yet.
4. Concept Dependency Graphs
Show what this module depends on and what later work depends on it.
5. Weekly Learning Journal
Track what stuck, what did not, and what needs another pass.
6. Checkpoint Gates
Use an honest pass/fail gate before moving into heavier prerequisite-dependent work.
7. Interleaved Review
Mix old and new material in quizzes and cumulative reviews so transfer is tested, not just short-term memory.
8. Dual Coding
Use both words and visuals for the same concept when the material benefits from a diagram or structured comparison.
9. Code Katas
Use short repeatable drills to build fluency instead of pretending one pass equals mastery.
10. Progress Tracking
Keep a visible record of modules completed, artifacts produced, and weak areas that still need remediation.
11. Warm-Up Quizzes
Activate prerequisite knowledge before a module starts so hidden gaps show up early.
Daily Learning Rhythm
- Review due cards or old notes briefly.
- Take the warm-up quiz or do a quick brain dump.
- Work through the concept pages.
- Do the drills, katas, or implementation work.
- Retrieve the idea from memory.
- Log what still feels weak.
Why This System Exists
It is trying to prevent common failure modes:
- reading as the default workload
- confusing familiarity with mastery
- producing no artifacts
- advancing with shaky prerequisites
- treating every semester page as equally complete
Anti-Patterns To Avoid
- Reading as the default workload: expensive, passive, and easy to fake
- Re-reading without retrieval: feels productive, usually is not
- Skipping artifacts: no notes, tests, diagrams, or writeups means weak evidence
- Advancing past checkpoints loosely: weak foundations become expensive later
- Treating all pages as equally complete: readiness labels exist for a reason