13_discipline — The Cadence Layer¶
You are not a monk. You are a viking. This distinction matters.
A monk renounces the world to purify himself. A viking sharpens iron in the evenings so he is ready when the season turns. You are the viking. You are not renouncing your job at Zoho, your family in whatever town, your friends, your weekends, or your right to be a full human being. You are training in the corners of your day for thirteen months so that when the season turns — when the study lands, when the ML-infra team opens a slot, when the segfault at 2 AM finally comes — the iron is sharp.
This layer exists because knowledge without cadence rots. You could read every K&R page and every Hacker News comment about restrict and volatile, and if you don’t build a rhythm around it, you will forget it faster than you learned it. C is unforgiving of ambient competence. It rewards ritual.
Why the discipline layer is separate from the technical layer¶
The technical layer (01_ through 08_) tells you what to learn. The tooling layer (11_tools_setup/) tells you how to set up the machine. The portfolio (12_portfolio/) tells you what to ship. This layer tells you how to survive thirteen months of doing it.
Most people don’t fail at C because they can’t understand pointers. They fail because month five arrives and they are tired, and there is no ritual to fall back on, so they stop for a weekend, and the weekend becomes a month, and the month becomes the end of the project. This layer is the ritual.
The 9 files¶
File |
One line |
|---|---|
|
The 2-week sprint model, S1–S26, with kickoff and retro templates |
|
The predict-then-measure habit — the single most important C-specific practice in this doc |
|
How to measure honestly, and the 7 sins of amateur C benchmarking |
|
The 30-min “C touch” every day, weekly rotation, the “no zero days” rule with mercy |
|
Feynman test, blog cadence, where to publish, the artifact IS the learning |
|
The 7 C-specific ways this can fail, with warning signs and correction protocols |
|
The Valley of Despair (M5–M7), the “brother” register, the anti-despair moves |
|
Sleep, exercise, the Bangalore heat, the wedding season, the “still a son” clause |
|
Converting rungs into offers: Zoho-internal, India, international remote |
How to use this layer¶
Read 01 and 04 in the first week — that sets your rhythm. Read 06 and 07 before you start Month 5 — you’ll need them. Read 08 any week your body sends a signal. Read 09 in Month 8, not before — premature study-prep steals from craft-building.
The discipline layer is not something you read once. It is something you re-read on the mornings when you don’t want to open the editor.
The closing doctrine¶
C rewards the patient. You cannot bluff a segfault, you cannot fake having read a stack trace at 2 AM, and you cannot compile your way out of a design you did not think through. Show up small, show up often, and after thirteen months of small honest days, the compiler will start telling you things it does not tell the tourists.
Return to ../README.md · Next: 01_sprint_cadence.md