08 — Health & Burnout

Brother, the plan is thirteen months. That is longer than a Netflix show, longer than a lot of relationships, longer than the memory span of an ambitious person’s motivation. Which means the plan will not be finished by intensity. It will be finished by not-quitting, and the enemy of not-quitting is not laziness — it is burnout.

Burnout is not a dramatic collapse. It’s a Wednesday afternoon in month seven when you cannot bring yourself to open the editor, and you cannot say why, and you feel guilty about it, and the guilt makes tomorrow worse. That is the shape of it. The body knew before you did.

This file is the physical layer of the roadmap. Read it before you need it.

The India-specific realities

Bangalore/Chennai summer

April through June and again in September, the heat is real. Not annoying — depleting. Combined with the AC-cold indoor cycle (28°C outside, 21°C in the office and at home), your body spends real energy on thermoregulation that could be going into deep work. This is not soft. This is measurable in cognitive-performance studies.

Practical:

  • Drink water on a schedule, not on thirst. Thirst signals late. A 1L bottle by your desk, refilled twice = 2L logged.

  • Add ORS or a pinch of salt + lemon to one bottle a day in peak summer. The AC-sweat cycle depletes electrolytes and you don’t feel it.

  • Don’t schedule sprint retros or deep work at 2 PM on a hot Saturday. That is nap-hour by biology. Move deep work to 9 AM – 1 PM.

  • Keep bedroom AC at 24–25°C, not 21°C. Cold sleep is not better sleep past a point, and it wrecks the throat by morning.

The 10 PM dinner trap

Indian household dinner routines land at 9–10 PM. You then eat, and by the time you’re horizontal, it’s 11 PM. Digestion is active. Sleep quality drops. You wake at 6:30 for the morning daily-practice slot foggy.

Practical:

  • If dinner cannot move earlier, at least stop eating heavy items by 9:30. Rice-heavy dinners the night before a Saturday deep-work block will cost you the first hour.

  • Walk 15 minutes after dinner. Not for exercise — for digestion. This is a real, measured, family-culture-compatible hack.

  • The one deep-dinner rule: one dinner per week (pick a night: often Sunday) is phone away, family only, no work, no roadmap, no scrolling. This is the sanity anchor. It’s non-negotiable. If it disappears you’ll notice it in your Sunday audit within 3 weeks.

Wedding season (Nov – Feb)

Brother, this is coming and you know it. Cousins’ weddings, colleagues’ weddings, family friends’ weddings. Multi-day events. Travel. Late nights. You cannot decline them all — and you should not.

Practical:

  • Look at your family / friend circle in October. Estimate: 3 weddings? 6? Circle them on the calendar now.

  • Pre-declare those weeks to yourself as light sprints. Reduce the sprint core to a single small task. Skip the stretch entirely. Do not try to catch up during the wedding — catch up in the following sprint by carrying over.

  • The wedding-week floor: 3 hrs of C++ instead of 11. That is fine. Missing entirely is what breaks the arc; showing up for 3 hrs keeps the muscle alive.

  • Do NOT drink through wedding season. One or two nights fine. Every wedding — you lose the mornings for a week. This is where the arc quietly dies for many Indian engineers.

Sleep is the load-bearing wall

Everything else in this roadmap is optional in a bad week. Sleep is not.

Target: 7 hours a night, minimum. Aim for 7.5.

Below 7 hours consistently and your gains on C++ collapse — not gradually, sharply. Memory consolidation of new syntactic patterns happens in slow-wave and REM sleep. You literally do not learn C++ without sleep. This is not motivational framing, it is neuroscience.

The moonlighting reality. You will sometimes trade sleep on a sprint. A rung is late, a bug is close to solved, the deadline for a blog post is Sunday morning. It’s 1 AM. You are tempted.

Do it consciously. Once every few sprints, a late night is acceptable. What kills people is the pattern — five nights in a row of “just one more thing” until 1 AM. That is where the burnout gradient lives.

Hard rules:

  • Trade sleep no more than 1 night per sprint, and never on a work-day (Zoho suffers before roadmap does, always).

  • The night you trade, sleep long the next day — protected long-sleep Saturday morning.

  • Never trade two nights in a row. Never.

Never catch up on the roadmap by cutting sleep. Catch up by cutting scope. This is the single most important line in this file.

Movement, the 90-minute minimum

Brother, you are going to sit a lot. Zoho hours + roadmap hours = potentially 12 hours of chair time on a big day. The body will punish you for that at M9. Back, neck, wrists.

Minimum: 90 minutes of movement per week. Split any way. Walking counts. There is no purity test here.

Suggested split for a moonlighting Zoho engineer:

  • Mon–Fri: 15 min walk after dinner (family + digestion + step count). 5 × 15 = 75 min.

  • Sat OR Sun: one longer thing. 30 min of anything — gym, badminton, cycling, a long walk in Cubbon Park or Besant Nagar. That’s 105 min total.

Wrist/eye stretches every 90 min at the desk. Not optional at M6+. Set a Pomodoro or a Time Timer. When the timer rings: stand up, roll wrists, look at a window for 20 seconds. This prevents the M9 injury that would end the arc.

Warning signs (do not ignore):

  • Wrist tingling after typing sessions → RSI onset. Fix immediately: split keyboard consideration, wrist rest, break frequency doubled.

  • Lower-back ache Sunday morning → chair or posture issue. Fix immediately.

  • Persistent headaches during deep work → hydration + screen distance + lighting. Check all three.

An injury at M6 is not a heroic sacrifice. It is roadmap-ending. Prevent it.

When to skip a sprint entirely

Some sprints should be skipped. Not “reduced.” Skipped. Zero C++. Zero roadmap.

Skip triggers:

  • Fever or serious illness. Recover first. C++ during dengue is not learning, it is punishment. Take the full illness sprint off.

  • Family emergency. Parent hospitalisation, sibling crisis, grandparent’s death. This is not a decision — the sprint is off, the roadmap waits. Follow ../99_pre_mortem/08_the_life_risk.md.

  • Wedding week for a first-degree relative or best friend. Not just an obligation — a genuine one. Sprint goes to family. Roadmap waits.

  • Mental-health dip. If for two consecutive weeks you feel flat, joyless, low motivation for things you normally enjoy — that is not a discipline problem. See the mental health section below.

Skipping is not failure. A skipped sprint with a note (“S12 skipped — Cousin B’s wedding + travel + Chennai grandmother’s health”) is a clean skip. The arc extends by 2 weeks. The plan handles it. You do not carry guilt.

The arc becomes 14 months instead of 13 if life demands it. It might become 15. The pitch you make at M14 or M15 lands the same as the M13 pitch. Recruiters do not have a stopwatch on your learning journey.

The mental-health honesty

Brother, this is delicate and I’ll say it directly. Two years of AI-assisted coding, feeling your own skill degrade quietly, is not just a technical problem. There is a self-worth undertone to “I used to be able to do this.” There is also grief there — low-grade, unnamed — for the twenty-two-year-old self who thought he’d already made it.

That grief is fine. It is also fuel, but only if you name it. Nameless grief in a moonlighting arc becomes months of low-grade motivation loss that looks like laziness.

Named signals of a real dip, not just a bad week:

  • Persistent flat mood 2+ weeks.

  • Loss of interest in things outside the roadmap too (movies, family, food).

  • Sleep problems: waking at 3 AM, unable to fall back.

  • Irritability with family for reasons that don’t match the stimulus.

  • The Sunday audit says “no inch moved” for 3 weeks.

Action:

  • Talk to someone. In India this is culturally under-used. Do it anyway. iCall, YourDost, or Manastha have reasonably-priced sessions. One session. Just one. Enough to name whether the dip is a phase or a signal.

  • Do not solve it by working harder on the roadmap. That is the reverse of what helps. Reduce roadmap scope for a sprint. Prioritise sleep, movement, family time. Return.

  • Talk to a friend who knew you at twenty-two. Someone who remembers the version of you who was fluent. This is grounding.

Mental-health dips do not end arcs unless they are ignored. Named and addressed, they cost 2–4 weeks of reduced scope, and the arc continues fine.

Non-negotiables

Brother, if this whole file collapses to a checklist, these are the four items:

  • Sleep: 7 hrs / night average. Trade rarely, cut scope first.

  • Movement: 90 min / week minimum. Any form.

  • One deep dinner / week with family, phone away. Non-negotiable.

  • One parent-facing hour per week, minimum. Phone call if not living with them. If living with them: one hour of undistracted time.

If any of these four is at zero for 2 consecutive weeks, roadmap paused until it’s restored. The plan is not worth trading these four for. Read ../99_pre_mortem/08_the_life_risk.md if you disagree with any part of this line.

Closing

Brother, thirteen months from now, if you have shipped six rungs and lost 8 kg and hurt your wrists and stopped talking to your mother, you have failed the arc even if the offer letter arrives. The offer is the excuse. The rebuild is the point. Be a viking, not a monk. Come out of this bigger, not smaller.

See you on Saturday morning.