04 — Daily Practice¶
The daily session is the atomic unit of this system. Not the sprint, not the phase — the session. Sprints and phases are how you think about direction. Sessions are how progress actually happens. One session per day, five days per week, for nine months. That is the commitment.
You will not always have 90 minutes. Some days you will have 30. On those days, 30 minutes of structured practice is not a consolation prize — it is the minimum viable session, and it counts fully. The only session that doesn’t count is zero.
The 30-Minute Minimum Viable Session¶
Use this on full workdays, deadline days, and any day where time is genuinely constrained. This is the floor, not the target.
Time |
Activity |
|---|---|
0–5 min |
Review — Pick one problem you solved in the past week. Don’t re-solve it. Re-explain it: out loud or in writing. What was the pattern? Why did it work? |
5–25 min |
Attempt — One new problem. Set a timer. Attempt independently for the full 20 minutes. If stuck at 20 minutes, read the approach only (not the code) and attempt again. |
25–30 min |
Record — Lab notebook: problem name, prediction vs. actual, one WHY sentence. |
The review step is not optional even in the 30-minute session. It is the mechanism by which spaced repetition works. Skip it and you are burning time on new inputs without consolidating existing ones.
The 90-Minute Deep Session¶
Use this on weekends and lighter workdays. This is the target format for most of Phase 0–5.
Time |
Activity |
|---|---|
0–10 min |
Warmup — Revisit a problem type from 2+ weeks ago. Attempt it under time pressure. Check if it’s faster than the first time. |
10–40 min |
Learn — Current phase concept work. Read the relevant section from your reference material, watch a targeted explanation, or derive the algorithm yourself on paper. No passive consumption: take notes. |
40–80 min |
Practice — 1 to 2 problems in the current phase pattern. Use the predict-then-measure protocol. For hard problems: 40 minutes per problem is appropriate — don’t rush. |
80–90 min |
Record — Full lab notebook entry: predictions vs. actuals, WHY sentences, open question of the session. |
The 5-Day Work Week Rhythm¶
Structure your week so learning and practice reinforce each other instead of competing.
Day |
Focus |
Session Type |
|---|---|---|
Monday |
Learn |
90-min deep if possible; 30-min min if not |
Tuesday |
Learn + first application |
90-min |
Wednesday |
Practice |
90-min |
Thursday |
Practice + variation |
90-min or 30-min |
Friday |
Review + sprint planning |
30-min review + sprint template fill |
Saturday |
Deep session or rest |
90-min deep (or full rest — see below) |
Sunday |
Metrics + lab notebook weekly entry |
30-min admin |
This rhythm is a default, not a constraint. If your Zoho workload means Wednesday is a 10-hour day, shift Wednesday’s session to Thursday. What matters is that the weekly cadence holds, not the specific day mapping.
Commute and Waiting Time (India Context)¶
If you commute by train or bus in India, you have 20–60 minutes of potential cognitive work time that most people waste. You cannot write code on a moving vehicle, but you can do:
Mental replay: Think through a problem you attempted yesterday. Can you trace the algorithm in your head without notes?
Audio: Algorithm-focused podcast episodes or YouTube lectures on concepts you’re currently studying (audio only, commute mode).
Pattern quiz: Close your eyes and quiz yourself: “What is the time complexity of Dijkstra’s? What data structure does BFS use? What’s the invariant of a sliding window?”
This is not primary practice. It is consolidation. 30 minutes of commute consolidation 5 days/week adds up to 2.5 hours of passive reinforcement that costs zero additional time.
When NOT to Practice¶
Practicing when you are in one of these three states is worse than not practicing. The session will produce no learning, create negative associations with the habit, and exhaust resources you need for the next day.
Physical exhaustion — If you are running on fewer than 5 hours of sleep, skip the session. Sleep is where the learning consolidates. A zombie session actively competes with consolidation.
Fever or acute illness — Your brain cannot form the connections that constitute learning when your immune system is consuming its resources fighting an infection. Rest is the correct protocol.
Acute stress event — A relationship crisis, a family emergency, a severe work conflict. These are not excuses. They are genuine cognitive load that makes deep practice impossible. Do one 5-minute review if you want to maintain the habit. Otherwise, give yourself permission to rest. See
08_health_burnout.md.
Recognizing these states honestly is harder than it sounds. The discipline voice says “push through.” The systems voice says “this session will cost you more than it gives you.” Trust the systems voice on these three conditions.
Navigation: ← Benchmark Hygiene | Teach to Learn →