Practice
Deliberate practice
Training and consuming content are two different things. Content gets you to knowing; training gets you to being able to produce it. The four kinds of deliberate practice here each map to one occasion: 20 minutes a day to keep your touch sharp, turning interview answers into evidence before an interview, layered fault isolation when something breaks, and writing code on a whiteboard.
92 questions and scenarios, every one with a pass standard — practice without acceptance criteria is not practice.
An eight-week schedule
| Time | What to do | Pass standard |
|---|---|---|
| Weeks 1–2 | Daily micro drills: 2 questions a day + 1 debugging scenario | The goal is not to answer correctly but to say it through once without looking; wherever you stall is your weak spot |
| Weeks 3–4 | Pick 8 interview questions for your target role + hand-write 2 | Record a 90-second voice answer per question and listen back: are there numbers, are there trade-offs |
| Weeks 5–6 | Debugging scenarios until you can draw the triage tree | Without looking at answers, write out the checks at each layer, then compare |
| Weeks 7–8 | Relearn the knowledge behind your weak spots + do a small experiment | Training only exposes problems; fixing requires going back to the knowledge and hands-on work |
Daily Micro Drills
32 questions, two a day, 20 minutes
32 questions · 6 groups
Interview Questions
By role, 24 questions, and what counts as a sufficient answer
24 questions · 6 groups
Debugging Drills
24 real faults: symptom → path → root cause
24 scenarios · 6 groups
Handwritten Implementations
12 whiteboard problems with interfaces and grading points
12 problems · 4 groups
How to practice correctly
Do not look at the answer; say it in three sentences. Where you stall is the weak spot. Go back to the matching topic page, relearn, come back and say it again. Reading answers does not create ability — that is why everything on this site carries a «how do you know you learned it» standard.