[Beginner] · The eight steps, and the three surfaces I learn on.
The loop
Learn → Write → Reconstruct → Practice → Check → Repeat → Apply → Synthesize
- Learn — read, watch, listen, attend the class, study the source.
- Write — physical notes, in my own words. The goal is understanding, not beautiful notes.
- Close the material — board or paper. Explain, derive, draw, reconstruct, or solve from memory.
- Practice — actual problems and examples.
- Check — compare against a solution or reference. Find the mistakes and the gaps.
- Repeat — go back to the hard parts until they’re familiar.
- Apply — use it in a real situation.
- Synthesize — only once it’s solid, write the clean digital version.
Step 3 is the one that gets skipped and the one that does the work. Rereading feels like learning. Reconstruction is learning.
The three surfaces
| Surface | Role | What happens there |
|---|---|---|
| The board | Arena / laboratory | Solve, reconstruct, test memory, make mistakes, erase, try again |
| The notebook | Workbench | Notes in my own words, worked problems, the mess |
| The laptop | Library | The final polished version — synthesis and reference only |
This is how it actually worked during JAMB. My notebooks recorded notes; the board was the real notebook. In class I often wouldn’t write the full solution — just the answer, unless it was something I knew I’d forget. Then at home I’d reconstruct the solution from memory, sometimes with a visual memory of myself or the teacher working through it, and use that to rebuild the process.
What that tells me about how I encode things:
- active recall beats rereading
- visual memory is a real asset
- physical writing matters
- reconstruction is the test
- retrieval, not recognition
Implication for this vault: the laptop comes last. A polished digital note written before I’ve reconstructed the material by hand is a note about something I don’t know yet. See AI as Sparring Partner — the same trap, automated.
Learning and doing are different
Reading about a thing changes how I think about it. Only practice determines whether I can do it.
Learn → Understand → Remember → Practice → Reflect → Repeat → Embody
Reading gets me to “remember”. Nothing past “practice” is available without reps. This is why Project Ideas exists in this vault and why fourteen domains here are honestly marked [reference] — notes are a map, not reps.
How this applies to DSA specifically
I’m restarting DSA from the beginning even though I’ve typed most of it before — not because I know nothing, but because I want the foundation rebuilt through active practice. Physical notebook. Call it SWE 101.
Per topic:
- Learn the concept.
- Write physical notes.
- Understand the underlying idea.
- Study one or two worked solutions.
- Identify the pattern.
- Close the solutions.
- Solve other problems independently.
- Practice repeatedly.
- Eventually write the clean understanding digitally.
The rule on worked solutions: don’t copy them, mine them for the pattern. Study 1–2 sliding-window solutions → understand what makes a problem a sliding-window problem → close the solutions → solve new ones cold.
Related: DSA course · LeetCode Patterns
Next: The Course System.
Software engineering
Infrastructure & security
Computer science
Hardware & engineering