13 — Discipline

The rhythm layer of the fortress. Everything above this file is what to build. Everything in this directory is how you keep showing up while you build it — for 13 months, alongside a full-time job at Zoho, in a Bangalore/Chennai summer, with a brain that has been outsourcing its thinking to AI for two years.

The frame: viking, not monk

You are not entering a monastery. You are not swearing off comfort, family dinners, weddings, weekend trips, or the occasional Netflix collapse. You are training like a viking who has to farm the land Monday through Friday — you show up, you sharpen the axe, you keep the boat seaworthy, and when the raiding season opens (M11-M13, study loops) you are the fittest man on the longship.

Monks fail this arc. Monks burn out at M4. Monks quit at M6. Vikings return in the spring, tired but alive, with something to show. Be the viking.

What the discipline layer IS

  • Rhythm: the 2-week sprint (01_sprint_cadence.md), the daily 30-minute floor (04_daily_practice.md), the Sunday audit (07_motivation_sustainment.md).

  • Hygiene: honest measurement of C++ code (03_benchmark_hygiene.md), predict-then-measure loop (02_lab_notebook.md), a lab notebook that catches the “I thought I remembered this” moments before they become bugs at M9.

  • Signal generation: teaching in public (05_teach_to_learn.md) — because output is how learning becomes permanent, and how a recruiter finds you in M11.

  • Threat modelling: knowing the 7 ways this specific arc dies (06_failure_modes.md) so you can see the failure coming a sprint before it lands.

  • Sustainment: the psychology of the Valley of Despair (07_motivation_sustainment.md), the physical layer (08_health_burnout.md), and the conversion machinery (09_interview_or_assessment_conversion.md).

What the discipline layer is NOT

  • Not a purity test. Not a streak-you-must-never-break vow.

  • Not performative hustle-culture. Nobody needs to see you posting “day 47 of 400” on LinkedIn.

  • Not self-flagellation. When a sprint slips, you diagnose using 99_pre_mortem/, cut scope, and continue. You do not punish yourself.

  • Not perfectionism. The goal is a working, shipped rung every phase — not a beautiful one.

  • Not a replacement for 99_pre_mortem/. Discipline handles the normal case. Pre-mortem handles the day the wheels come off. Both files exist for a reason.

The 5 principles

  1. Cadence beats intensity. 10 focused hours across a week compound; one 30-hour weekend followed by two dead weeks does not.

  2. Ship every rung. No rung is done until something is committed, pushed, and (from M3 onward) shared publicly, even if only to r/cpp weekly show-off.

  3. Predict before you run. Every serious code session opens with a 1-line prediction. This is how a returning-dev brain rebuilds intuition — by surfacing the gaps between “I think I remember” and “I actually know”.

  4. Measure release, not debug. C++ discipline is bench discipline. If you cannot say what compiler, what flags, what hardware, and what baseline, you did not measure anything.

  5. The roadmap serves you. Not the other way around. Life ranks above the plan. Family ranks above the plan. Sleep ranks above the plan. When life demands a pause, take one — see 99_pre_mortem/08_the_life_risk.md.