08 — Health & Burnout

A thirteen-month project run on top of a full-time job is a load-bearing structure, and every load-bearing structure has a foundation. Your foundation is your body and your relationships. If either cracks, the C roadmap comes down with it — not because C is fragile, but because you are the runtime. This file is the maintenance manual for the runtime.

Sleep is non-negotiable

Seven hours minimum. Every night. A debugged 90-minute session beats a fatigued 4-hour flail every time. This is not a productivity slogan; it’s how C works. Debugging is pattern-matching under uncertainty, and sleep-deprived pattern-matching produces false positives — you “fix” the wrong line, you introduce a subtler bug, you spend the next Saturday paying interest on last Saturday’s tiredness.

Rules:

  • Bed by 11 PM latest if you are doing the 6 AM slot from 04_daily_practice.md.

  • No screens in the bedroom on weeknights. Charge the phone in the kitchen.

  • If you have to choose between finishing the sprint deliverable and getting your 7 hours — choose the sleep, and move the deliverable. Every time.

  • Weekend catch-up sleep exists but is not a substitute. Do not run a 5-hour weekday and think Saturday will heal it.

Exercise 3× per week, minimum

Even bodyweight. Even 20 minutes. C debugging is a cognitive-load beast, and cardio protects cognitive load the way regular oil changes protect an engine.

What counts:

  • 30 minutes of walking, briskly, outdoors. Yes, that counts.

  • Bodyweight circuit at home: pushups, squats, planks. 20 minutes.

  • Actual gym session, cycling, swimming, whatever you enjoy.

  • Sport with friends — badminton, cricket, football. Bonus: it doubles as socializing.

What does not count: yoga you don’t sweat during, stretching alone, “walking to the printer.” You need the heart rate up, three times a week, minimum. This is not vanity, it is cognitive infrastructure.

India-specific: the seasonal calendar

You are not learning C in a climate-controlled vacuum. You are learning C in India, and India has weather and seasons that will affect your capacity. Plan for them.

April–May: heat and power cuts. Bangalore hits 35°C+ and Chennai worse. Concentration drops. Power cuts interrupt long sessions. Plan LIGHTER sprints in April-May. Reduce the deliverable ambition by 30%. This is not weakness, it is climate-aware planning. Use the mornings hard (6–8 AM before heat) and the evenings light. Air-conditioned coffee shops (Third Wave, Blue Tokai) are legitimate offices in these months.

October–February: wedding season. Cousin weddings, friend weddings, family functions, festivals. Your personal-time budget can drop from 12 hours to 3 hours in a bad week. Build ONE buffer sprint into Q4 explicitly (see 01_sprint_cadence.md — S20 or S22 candidates for this). Do not fight the wedding season. Attend the weddings. Be present. Show up in the shirt your mother picked. Scale down the sprint, do not skip the family.

Monsoon (June-Sept in Chennai, less severe in Bangalore). Power stability varies, commuting eats hours, mood dips are real. Nothing structural to change, just be forgiving about slipped sprints in these weeks and log “weather” honestly in the retro.

The “still a son, still a friend” clause

One deep dinner per week with family or a close friend, no phone. Not “in the same room as family while I code.” A real meal, phone in another room, conversation. This is not a productivity hack. This is the clause that keeps you from becoming the guy who finished M13 on schedule and lost his family in the process.

Once a month, minimum: a full day with no C. Not “a rest day where I read one chapter.” A day. See friends. Take your parents somewhere. Watch a movie in an actual theatre. Come back Monday with a mind that has been elsewhere.

Repetitive strain: the boring, essential rules

C coders spend a lot of time hunched over debuggers, and the injuries that end programming careers are almost always physical, not mental. Prevention is cheap; recovery is not.

  • 60-minute pomodoros with 5-minute stretches. Get up, walk around the room, roll the shoulders. Every hour. No exceptions.

  • Monitor at eye level. If you’re staring down at a laptop screen for hours, your neck will file a complaint after 6 months. External monitor + laptop-as-keyboard on a stand is the cheap fix.

  • Forearm-neutral keyboard. A mechanical keyboard is not mandatory, but keyboard height matters. Wrists straight, not angled up. If you feel a twinge in your wrist that lasts >2 days, address it immediately — tendinitis is a 3-month problem once it starts.

  • Blue-light discipline is overblown, but distance is not. 20-20-20 rule: every 20 minutes, look at something 20 feet away for 20 seconds. Your eyes will thank you at Month 8.

Signs of burnout — specific to this journey

Generic burnout advice is generic. Here are the burnout signs specific to a 13-month C project on top of a full-time ML job:

  1. Hating the moment you open the editor. Not tired — dreading. If you dread opening VSCode/nvim/Emacs for 5 consecutive weekdays, that is burnout, not laziness.

  2. Snapping at family. You come home from work and someone asks a normal question and you snap. This is not them; it is you being over-capacity. If this happens twice in a week, you’re past sustainable load.

  3. Physical fatigue that sleep doesn’t fix. You slept 8 hours and still feel tired. For one day, whatever. For 5 consecutive days, something is systemically wrong.

  4. The joy leaving even the small wins. You get a segfault fixed after an hour and feel nothing. You ship a benchmark post and feel nothing. If wins are joyless for 2 weeks, the roadmap is extracting more than it’s giving, and needs adjustment.

  5. Ambient irritability. Everything mildly annoys you. Traffic, meetings, Slack, family, the compiler. All of it.

If any TWO of the above show for 5 consecutive days, pause the sprint. Not the daily practice, not the discipline — the sprint deliverable. Drop back to the 30-min daily touch and nothing else, for one full week. Sleep, exercise, eat, see family. Then reassess. If the symptoms recede, resume the sprint at reduced scope. If they don’t, apply the full reset protocol from 99_pre_mortem/09_summary_and_reset_protocol.md and consider whether the roadmap needs a longer pause.

The physical checklist you review at every sprint retro

At every Sunday retro, alongside the technical review, ask yourself:

  • Did I sleep 7+ hours the majority of nights this sprint?

  • Did I exercise at least 6 times across the two weeks?

  • Did I have at least 2 phone-free meals with people I love?

  • Did I have at least one full day away from the laptop?

  • Any pain, twinges, eye fatigue, back issues to note?

If three or more answers are “no,” the next sprint must include physical corrections BEFORE new deliverables. This is not optional. This is how you make sure the 13-month runtime survives to see M13.

Return to README.md · Next: 09_interview_or_assessment_conversion.md