Lesson 43.2 · The Core 100
Solving and Revising Well
Solve, then re-solve from a blank file after 1, 3, 7 and 21 days. Track the pattern, the key insight and the mistake for every problem you missed.
10 min
Think of it like this
Learning a language: you remember the words you were asked to recall on day 2, day 5 and day 12, not the ones you read once.
1.A routine per problem
1. Read and name the pattern (Module 42's checklist). 2. Say the brute force and its complexity. 3. Find the bottleneck and the optimisation. 4. Code it, then test on the examples and one edge case by hand. 5. Compare with the course solution, including other approaches.
Keep a revision log with four columns: problem, pattern, key insight in one line, mistake made. Re-solving from the log on a spaced schedule (1, 3, 7, 21 days) turns a solved problem into one you can produce under pressure.
Quick check
You solved a problem only after reading hint 2. When should you see it again?
Remember
- Brute force first, out loud.
- Log pattern + insight + mistake.
- Spaced re-solving.
Common mistakes
- Counting a problem as learned after reading its solution once.