Weekly Rhythm — The Canonical Week

Full-time job at Zoho + 10-15 personal-time hours/week. India / Bangalore or Chennai calendar. Applies from S1 (July 6, 2026) through S26 (July 5, 2027).

The fortress will not survive if you rely on inspiration. It survives on schedule. This file names the specific hours of the specific days you will do the work. If you deviate from the schedule twice in a sprint, the schedule is wrong — not you. Adjust the schedule and note it in the sprint retro.

The canonical week below assumes: 5-day office/hybrid Zoho week (roughly 9:30 AM – 6:30 PM), one weekend day for family/rest, one weekend day for a deep block. If your Zoho week runs differently, translate the block structure, not the times.

The Canonical Week At A Glance

Weekly total (target): 12 hours personal-time. Range: 10-15.

Weekday Blocks (Monday to Friday)

06:30 – 08:00 — The Morning Deep Block (90 minutes, MANDATORY)

This is the block that runs the fortress. In India, before 8 AM, three things are true: nobody at Zoho is Slacking you, family/roommates are asleep, and Bangalore/Chennai are not hot yet (except May-June, when this becomes even more valuable). Do the hardest cognitive work here.

What lives in this block by phase:

  • P0-P1 (M1-M2): Beej’s Guide / Modern C reading + typing every example

  • P2 (M3): Memory & pointers exercises

  • P3 (M4-M5): One NeetCode problem in C (aim for 45-60 min per problem)

  • P4 (M6-M7): One syscall exercise, or nsh feature build-out

  • P5 (M8-M9): Pthreads / networking exercises, then epoll server

  • P6 (M10-M11): Matmul / SIMD kernels, roofline plotting

  • P7 (M12-M13): Reading production code, PR iteration

Rules:

  • Phone in another room. Not silenced — in another room.

  • No email/Slack. No Zoho work. This is not office overflow.

  • Editor + terminal + man pages + Compiler Explorer. Nothing else.

  • If you finish early (rare), start the next thing. Do not scroll.

21:30 – 22:00 — The Evening 30-Min Touch (30 minutes, MANDATORY 5 days/week)

This block exists to prevent the “forgetting curve” between morning sessions. It is small on purpose. It is not for hard work.

What it is used for (rotating):

  • Monday: Read one chapter of the current book (Beej / Modern C / K&R for reference)

  • Tuesday: Review yesterday’s lab notebook entry, add follow-up if needed

  • Wednesday: One man 2 <syscall> page cover-to-cover

  • Thursday: Read one blog post from 09_resources/06_blogs_and_newsletters.md

  • Friday: Watch one 20-30 min Low Level (Low Level Learning) or Eskil Steenberg video

Rules:

  • Not a code-writing block. Writing at 21:30 leads to bugs and short sleep.

  • Bed by 22:45 latest. Sleep is the deliverable.

  • If you miss 3 in a row, you are in a yellow zone (see 02_sprint_calendar.md).

Weekend Blocks

Saturday 08:00 – 12:00 — The Deep Block (4 hours, MANDATORY)

This is when the sprint’s headline deliverable moves. If you have one uninterrupted 4-hour block in your week, this is it. Weekday mornings are for practice; Saturday morning is for shipping.

What lives in this block:

  • Writing the actual code for the current portfolio rung

  • Extended debugging (the 90-minute weekday block is too short for a nasty gdb chase)

  • Reading long-form production code (llama.cpp, valkey, curl)

  • Writing a blog post draft when a rung is nearing ship

Rules:

  • Coffee/chai fine. Breakfast before or during (protein > sugar).

  • No family/friend commitments before 12:30 PM in this window. Non-negotiable except emergencies.

  • If you’re in Bangalore/Chennai summer heat: AC or fan mandatory, hydrate.

  • If you have a wedding, funeral, or family emergency: skip the block, note it in the retro, do not double-block Sunday to compensate.

Saturday 12:00 onward — Life

Go live your life. Family. Friends. Partner. Food. Sleep. Movies. Whatever you do that keeps you sane and human. This is not “C study extended.” This is deliberately not-C time.

Sunday 09:30 – 11:00 — The Reading Block (90 minutes)

Sunday is deliberately lighter than Saturday. Reading, not typing.

What lives in this block:

  • Reading (books, blogs, papers) not directly attached to today’s task

  • Skimming what’s coming in the next sprint

  • Reading one section of 08_production_and_mastery/01_reading_production_code.md

  • Reviewing the week’s lab notebook entries for patterns

Rules:

  • Coffee, sofa, laptop. Do not open the terminal.

  • Physical notebook allowed for reading notes (this is not the lab notebook — different tool, see 13_discipline/02_lab_notebook.md).

Sunday 19:00 – 19:30 — The Sprint Retro (every second Sunday only)

Every second Sunday, the sprint ends. Retro happens. Template in 02_sprint_calendar.md. Close the laptop by 20:00. Do not spiral.

Rules:

  • No decisions about the roadmap after 20:00 Sunday. Ever.

  • If you feel the urge to quit, escalate, or replan on Sunday night — that’s the urge, not the reality. See 13_discipline/07_motivation_sustainment.md.

  • Real decisions get made on Saturday morning at 08:00. Rested. Alert. Chai in hand.

Weekly Total — The Math

Block

Days

Hours/day

Weekly hours

Weekday morning deep block

Mon-Fri

1.5

7.5

Weekday evening 30-min

Mon-Fri

0.5

2.5

Saturday deep block

Sat

4.0

4.0

Sunday reading block

Sun

1.5

1.5

Sunday retro (every 2nd)

Sun/2

0.5

0.25

Total

15.75

Range in practice: 12-15 hours in a green week, 8-11 in a yellow week (skipped 2-3 evening blocks or one Saturday), 4-6 in a red week (health, family emergency, wedding). Anything below 4 hours in a week and you are in a full-week pause — that’s fine, note it in the retro, resume the next Monday.

Slippage Rules — Green / Yellow / Red

Most weeks will not be textbook. Here’s how to react without spiraling.

GREEN Week (target)

  • All 5 weekday morning blocks hit

  • Saturday deep block hit

  • Sunday reading block hit

  • 12-15 hours logged

  • Action: Nothing. Keep going.

YELLOW Week

  • 3-4 weekday morning blocks hit (missed 1-2)

  • OR Saturday partial (2-3 hours instead of 4)

  • OR skipped the evening 30-min for 3+ days

  • 8-11 hours logged

  • Action: Note in lab notebook. Do NOT front-load next week to compensate. Scope-cut next sprint by 20% if it happens twice.

RED Week

  • ≤2 weekday morning blocks hit

  • OR Saturday block skipped entirely

  • OR sleep dropped below 6.5h average

  • ≤6 hours logged

  • Action: Read 13_discipline/08_health_burnout.md. If red-week is health-driven, take the following week off entirely. If it’s Zoho-driven, that’s a separate conversation — see 06_background_alignment.md. Do NOT double-block the following week.

Do not compound. Two red weeks with no rest between = burnout. Two yellow weeks with front-loading = injury or burnout. The schedule is not a debt.

India-Specific Notes

The Weather Slot

  • Mar-Jun (Bangalore/Chennai heat): Morning 06:30-08:00 block is the only comfortable block. Evening 21:30 is often still 28-30°C indoor without AC. Prioritize morning ruthlessly.

  • Jul-Sep (monsoon): Power fluctuations more common. Save every 5 minutes (git commit, editor autosave). Charge laptop at the start of blocks.

  • Oct-Feb (cool): Everything easier. Evening 21:30 is pleasant. Take advantage — this is when you can push toward 15h/week.

The Family / Social Slot

  • Family dinners. One “deep dinner” per week (Wed or Fri) with family, no phone, no laptop — required, see 13_discipline/08. This is not roadmap-negotiable.

  • Wedding season (Nov-Feb, and April-May). Expect to lose 2-3 weekends in Nov-Dec and 1-2 in April-May. Schedule buffer weeks around them (see 02_sprint_calendar.md).

  • Festival season (Onam Sep, Diwali Nov, Christmas Dec, Pongal Jan, Holi Mar). Scope down the corresponding sprint by 20-30%.

The Zoho Slot

  • Zoho quarterly cycles. If your team has Q-end pushes (calendar or fiscal), anticipate 2-3 weeks of compressed personal time each quarter. Do not front-load; scope-cut instead.

  • Zoho oncall or release week. If you’re on release week and it’s a heavy sprint, negotiate load reduction with your future self in the sprint template.

  • Zoho commute. If commute > 60 min each way, morning deep block becomes hard — consider moving to a hybrid arrangement, or shifting the block to 06:00-07:15 with lower total but earlier start. Talk to your manager about hybrid; frame it as “deep work in early morning” not “personal project.”

The 6:30 AM Question — Why Not Just Evenings?

You will be tempted, especially early, to move the deep block to 10:00 PM - midnight. This is the most common personal-time-hour mistake for engineers in India who are morning-averse.

Three reasons the 6:30 AM slot wins:

  1. Cognitive: willpower is depleted after a Zoho workday. Morning is when your prefrontal cortex is expensive-suited. C programming, gdb, ASan output, integer promotion rules — these need expensive prefrontal cortex, not tired-brain.

  2. Signal integrity: Bangalore/Chennai at 6:30 AM has no Slack notifications, no family movement, no delivery boy at the door, no roommate cooking. At 10:00 PM there are all four.

  3. Sleep debt: working till midnight compounds sleep debt across weeks. The Valley of Despair (M5-M7) is 3x worse on 6h sleep than on 7.5h. This is the single strongest predictor of quitting.

If morning is genuinely impossible for you (night-shift Zoho team, chronic morning sickness, or a physical reason), replace with 20:00-21:30 block — not 22:00 or later. Bed by 23:00 at the latest. Non-negotiable.

When To Deviate

You may deviate from the canonical week without guilt in these cases:

  • Family emergency. Full stop. Skip everything. 99_pre_mortem/08 applies.

  • Illness ≥ mild flu. Sleep and hydrate. The compiler will wait.

  • A wedding you actually want to attend. Go. Log the skip. Move on.

  • A rare Zoho crunch that lasts a specific week (release cutover, oncall firefighting). Log it. Do not overcompensate the next week.

  • A rung is close to shipping and needs one extra Saturday push. Once per rung. Not every rung.

You may not deviate from the canonical week for:

  • Motivation issues alone (that’s what 13_discipline/07 is for, not calendar hacks)

  • “I want to binge YouTube” (fine — but do it in Saturday 12:00 onwards, not deep block time)

  • “I’ll do double next week” (this is the compound-injury trap)

  • LLM landscape panic (“C is dead, why am I doing this”) — read 99_pre_mortem/06, don’t skip the block

The Meta-Rule

The canonical week exists so you never have to decide, in the moment, whether to work. The decision was made in advance, by you, at the start of the fortress. Deciding daily is exhausting; the schedule pre-decides.

Do the block. Close the laptop. Repeat 91 times.

Return to README.md · Previous: 03_north_star_artifacts.md · Next: 05_kpi_dashboard.md