Pre-Mortem 08 — Life, Health, and Family¶

Failure Mode: Life events, health, and family obligations colliding with the plan.
Probability: CERTAIN — 100%
Peak Risk Period: Always. This is not a failure mode you prevent. It is one you survive.

This file is different from the others.

Every other pre-mortem file is adversarial — it names a failure mode you can avoid if you’re disciplined enough, self-aware enough, skilled enough. This one isn’t. This one is about the things that will happen regardless of how disciplined you are. A parent’s health. A relationship that needs you. A festival season that belongs to your family. A mental health week that is not optional. A work crisis at Zoho that demands everything you have for 3 weeks.

These things are not interruptions to your life. They are your life. The plan is a tool in service of that life. This file is here to make sure the tool never gets confused for the thing it serves.

Read this before you start. Read it again when something hard happens. Keep it somewhere you can find it in 30 seconds.

What It Actually Looks Like¶

Brother, let me be direct about what this failure mode produces, so you can recognize it when it comes.

Scenario 1: You are 6 months in. Real progress — graphs are starting to click, you’ve submitted your first Codeforces problem, your lab notebook has 18 weeks of entries. A parent falls ill. Not catastrophically — but enough that you spend 3 weeks at their side, managing logistics, being present at the hospital, making the calls that need to be made. You don’t open LeetCode once. You return to your desk and look at the plan. Six months of momentum. Three weeks gone. The guilt lands hard. “I ruined it.” You don’t restart because restarting feels like admitting to yourself how far behind you are. The guilt becomes the reason you can’t return. The plan ends not because of the illness — but because of the shame about the illness.

Scenario 2: Diwali 2026. Your family expects you present and actually present — not half there while mentally tracing a graph traversal. You try to do both. The festival becomes a distraction from the plan. The plan becomes a weight on the festival. You are fully present for neither. The family remembers you as distracted. You remember the festival as stressful. You’ve paid the cost of two things and gotten the value of neither.

Scenario 3: Zoho enters a high-pressure product deadline period. Three weeks of 10-11 hour days. You’ve been doing evening DSA sessions after work. You continue trying to do evening sessions. By week 2, the sessions are 30-minute zombie sessions where nothing sticks and you’re operating at 60% cognitive capacity. The sessions aren’t teaching you anything — they’re burning residual energy you need for recovery. But you continue because the plan says you should. By week 3, you resent both the job and the plan. The resentment is the early warning sign of burnout.

Scenario 4: You haven’t been sleeping enough for 6 weeks. Small shortfalls — 6 hours instead of 7.5, consistently. You don’t notice the degradation because it’s gradual. Your pattern recognition in practice sessions is worse. Your retention is worse. Your problem-solving is slower. You interpret this as “hitting a plateau” and try to practice more to compensate. You are making yourself worse and diagnosing it as insufficient effort.

You deserve better than any of these outcomes. This file is the prevention.

The 3 Rules That Override the Plan¶

These three rules take precedence over every sprint commitment, every exit criteria, every weekly target in the entire fortress. If any of these is violated, nothing else in the plan is working correctly.

Rule 1: 7+ Hours of Sleep. Always.¶

Brother, this is not negotiable and it is not soft. Sleep is the consolidation window. When you learn an algorithm and sleep on it, your hippocampus replays the learning during slow-wave NREM sleep and transfers it to long-term cortical storage. When you cut sleep, that transfer doesn’t happen. You spent the session. The learning didn’t stick. You’ve done the work and discarded the output.

Staying up until 1am to fit in a session is not discipline. It is borrowing against tomorrow’s learning to log tonight’s session. The debt is real. It accumulates. By week 3 of sleep deficiency, your working memory is functionally impaired — and working memory is exactly what you need for algorithm design.

The rule: No DSA practice after midnight. If it’s past midnight and you haven’t started — don’t start. Log it as skipped. Sleep. Do it tomorrow. Tomorrow’s well-rested session is worth more than tonight’s depleted one.

Rule 2: Movement, Minimum 3x Per Week¶

A 30-minute walk. A cycle. Cricket on Sunday. Whatever you do — move. Sedentary cognitive work for 12+ hours degrades prefrontal cortex function, and prefrontal cortex is the seat of the deliberate, effortful reasoning that DSA requires. This is not abstract. You will feel the difference on days you’ve moved versus days you haven’t.

The bar is low deliberately. 30 minutes. Three times. That’s it. Track it in your lab notebook — not as an achievement, as a check.

Rule 3: One Full Rest Day Per Week¶

Not a “light practice day.” A full rest day. No DSA, no guilt about no DSA, no mental rehearsal of algorithms while pretending to be present with family. A day that belongs entirely to other things — rest, people, food, whatever you actually enjoy.

The plan accounts for this. Sunday is default. It can move to Saturday if needed. It cannot disappear.

Burnout Signals Specific to This Context¶

These are the early warnings that you are heading toward breakdown, not plateau:

Signal	What It Means
You’re solving problems but resenting them	You’ve been pushing past exhaustion. Reduce scope immediately.
You skipped sessions and feel nothing about it	Apathy > guilt = advanced burnout. Not laziness. Stop and rest.
You’re using AI to generate solutions and counting them	You’ve already left the plan mentally. The body is still going through motions.
You read a problem and feel dread	Your nervous system has associated practice with threat. Rest required before continuing.
Practice sessions feel like debt repayment	The relationship with the plan has inverted. The plan is costing you more than it’s giving.

Guilt about skipping is actually a healthy sign — it means you’re still engaged. The dangerous state is when skipping feels like relief with no tension. That is the signal that says: stop and rest, not push harder.

The Permission Slip¶

Brother.

I am giving you explicit, unconditional permission to pause this plan. Not a tense pause with a guilt-laden return date hanging over you like a debt — a clean pause. A real one. The kind where you put the laptop away, stop counting days, and go be a full human being.

I know what you came here for. You wanted to find sense in what you’re doing. You wanted to build something real — something that belongs to you, something that AI can’t generate in 30 seconds. That want is real and it matters. It deserves respect.

But it does not matter more than your parents. It does not matter more than your health. It does not matter more than being fully present at a festival that happens once a year, with people you love, in a home that shaped who you are.

If a parent gets sick — stop. Be there. Completely. Not half-present with one eye on a graph traversal problem. Be there. The algorithms will be exactly where you left them when you return.

If a relationship needs you — stop. Give it what it needs. Algorithms do not need you back. People do.

If your mental health needs a week — not “I’ll do 30 minutes a day” week, but a real week of rest and recovery — take it. One week of genuine rest recovers more learning capacity than three weeks of zombie sessions running on fumes.

If Diwali needs your full presence — give it. Five days. Fully there. The plan was already designed with this protected. You are not breaking anything by living your life.

If Zoho enters a crisis month — work the crisis. Do not try to carry both at full intensity. Choose consciously, without shame: it is okay to put the plan down for a month during a genuine work emergency. You can pick it back up.

The plan has a restart protocol. It is forgiving. It does not care how long you were gone — 2 weeks, a month, 6 weeks. It only asks one thing when you return: one 30-minute session. Then one more. That is the entire requirement.

You are not a DSA learning machine. You are a person trying to build something meaningful in the margins of a demanding life. That context deserves respect, not a system that breaks you by Month 5 because it didn’t account for being human.

Pausing is not failing. Abandoning is a choice — and it only becomes real and permanent if you choose not to restart. The restart protocol exists specifically so that no pause has to become abandonment.

Take care of your parents.
Take care of yourself.
Take care of the people you love.

The algorithms will still be there.

Dates to Protect — Mark These Now¶

Open your phone calendar and mark these as protected before you close this file. The sprint calendar in 01_sprint_cadence.md already accounts for them. You are not losing ground by honoring them.

Event	Dates	What “Protected” Means
Diwali 2026	October 20–24, 2026	5 days — no practice obligations. Full presence.
Christmas / New Year	December 25 – January 2, 2027	8 days — minimum practice, maximum rest.
Pongal 2027	January 14–17, 2027	4 days — no practice obligations.
Any family health event	Unlimited	There is no sprint that matters more than this. None.
Mental health week	As needed	If you need one — take one. No justification required.

The Restart Protocol¶

When you’ve been away — for any reason, for any duration:

Open this file. Read the permission slip.
Write in your lab notebook: “I am returning on [date]. I am not behind. I am here.”
Do one 30-minute session using the minimum viable format from 04_daily_practice.md in the discipline section.
Continue.

No punishment sessions. No “I have to make up for lost time.” No catching up. No shame. Just the next session. That is the entire protocol. It works every time, for any duration of absence, for any reason.