Pre-Mortem 08 — The Unspeakable File

Brother, this one isn’t about kernels.

Failure vector: A parent’s health scare. A relationship ending. Your own body giving out from months of poor sleep and no exercise. Falling in love. A wedding you have to attend. A friend who needs you. A life event that has nothing to do with inference engineering and everything to do with the fact that you are a human being living a life, not a build process running to completion.

Probability this hits in some form: ~85%. Some version of this will land. Not maybe. Almost certainly.

Why This File Exists

Every other file in this pre-mortem is technical. Failure modes with parries. This one is different, because there is no parry for a father’s heart attack, and there shouldn’t be.

You signed off your original message with “please help your son man.” I heard it. So this is the file where I say the thing that a mentor who actually cares has to say: the roadmap serves you. You do not serve the roadmap. If life comes for you, you drop the roadmap and go be a human being. No apologies. No debt. No shame.

I’m writing this in month 0 so that in month 7, when it hits, you don’t have to make the decision from a place of guilt. The decision is already made. Here it is, in writing, in your own repo:

Permission slip: You are allowed to pause the roadmap for as long as life needs you. The 13-month clock stops when you say it stops. The clock is a construct. You are not.

Signed, the version of you that wrote this in July 2026, when things were calm.

Print that. Put it in a drawer. Or don’t — the file itself is the artifact.

The Real Scenarios

Let me name them, because naming reduces the paralysis when they arrive.

1. A Parent’s Health Event

You live in Tamil Nadu. Your parents are aging. At some point in the next 13 months, one of them will have something — a fall, a diagnosis, a surgery, a scare. In India, in our families, you go. You show up at the hospital. You handle logistics. You lose 2–6 weeks of the roadmap.

What to do: Go. Fully. Do not open the laptop at the hospital to “just review one PR.” The presence is the point. When you come back, log the pause, adjust the sprint calendar, resume. The skill compounds over decades; two weeks is a rounding error. Two weeks of not being there for a parent is not a rounding error — it’s a wound that outlasts any career.

2. A Relationship Ending, or Beginning

Heart-shaped things distort time. A breakup around month 5 will hollow you out for a full month; the retro entries will get shorter, then stop. A new relationship around month 8 will (rightly) reprioritize your evenings; the roadmap will feel less urgent.

What to do: Let it be what it is. If a relationship is ending, grief needs air, not distraction. Take a genuine week off from the roadmap — not a fake week where you feel guilty the whole time. If it’s beginning, negotiate a rhythm with them; a good partner will understand “I have 90 minutes tonight” if you’re honest about it. The roadmap absorbs both. The people in your life do not have infinite patience for a partner who’s mentally somewhere else.

3. Your Own Body

At month 6, if you’ve been sleeping 5 hours a night, skipping meals, and coding until 2am on weekends, something will break. Back pain. Vision blur. A panic episode. A stress rash. Digestive issues. Bodies keep receipts.

What to do: The rules in 13_discipline/08_health_burnout.md are not suggestions. They exist because I’ve seen enough people burn out at month 6 of a 13-month plan to write the file with real conviction. Sleep 7–8 hours. Lift 3× a week. Walk daily. If your body sends a warning, take it. A doctor’s visit is not a failure of discipline; ignoring the warning is.

4. A Wedding Season

Indian family life is not a distraction. It’s the fabric. Cousins get married. You travel to Chennai or Coimbatore or Bangalore or wherever. You spend three days out of a laptop. You sleep in a strange bed. You come back tired.

What to do: Schedule them into the sprint calendar deliberately. “Weeks of Nov 12–19 = wedding travel; deliverable for that sprint is a reading task, not a build task.” Don’t try to bring the laptop and fail to open it and then feel guilty. Plan for real life. Sprint 22’s deliverable can be “read the FA3 paper on the train and take notes” — that’s a legitimate sprint output.

5. A Friend Who Needs You

A close friend calls at 11pm on a weekday because something in their life is falling apart. You have a benchmark script running. What do you do?

You pick up the phone. You go to their apartment if you have to. The benchmark waits. This is not even a hard decision — I only write it here because sometimes ambitious people forget that no career is built on the ashes of the relationships that made the career possible.

6. Falling in Love With Something Non-Technical

Maybe halfway through, you rediscover music, or writing, or hiking, or a sport. Suddenly evenings feel too precious to spend in Nsight Compute. This is not a failure. This is a life reasserting itself against a monastic sprint.

What to do: Honor it. Adjust the ratio. Instead of 15 hours/week, do 10. Extend the roadmap to 18 months instead of 13. You are not defecting from the plan; you are refactoring it against reality. The best engineers I know all have a rich non-technical inner life. It’s not competing with the work; it’s the ballast that keeps the work sustainable.

The Rules (Non-Negotiable)

  1. Life comes first. Always. No exceptions. This is not a rule you should have to be reminded of, but ambitious plans make people forget it. Reminded, now, in writing, in your own repo.

  2. The 13 months are a construct; the skill is career-long. A 3-month pause loses 3 months. It does not lose the plan. It does not lose you. Inference engineering as a field will still exist in 2028, 2030, 2035. You have decades. You do not have 13 months and no more.

  3. Tell someone. Not everyone. One or two people close to you should know what you’re doing, so they can support you (not just hold you accountable). Isolation is the multiplier on every other failure mode. In file 03 (03_burnout_month_6_to_8.md) we said community is the parry against isolation — that’s engineering community. This is the other kind: your mother, your best friend, a mentor. Someone who cares about you as a person, not as a project.

  4. Build slack into the plan. Plan 15 months of effort in 13 months of calendar. Have buffer weeks every quarter. When life hits, the buffer absorbs the impact instead of the deliverables. 00_command/ should reflect this — there should be four “buffer weeks” reserved and not populated with sprints.

  5. Do not measure life the way you measure kernels. Do not have KPIs for your relationships. Do not “optimize” your visits home. The habits that make you excellent at inference engineering (predict, measure, minimize slack) are exactly the wrong habits for the human parts of your life. Learn to switch modes.

  6. India-specific: family obligations are not optional. Weddings, funerals, festivals, hospital visits, siblings’ milestones. These are the fabric of the life you’re building the career to support. Fighting them is a category error. Schedule them, don’t fight them.

  7. If you fall in love, tell them what you’re doing. Not on date one. But early. “I’m committing hard to a 13-month plan; here’s what it means for our time together. What do you need?” A good partner will negotiate the rhythm. A partner who won’t isn’t the right partner for a person on a 13-month build.

The One-Line Check

When something in your non-technical life comes for you, ask this:

Ten years from now, will I regret pausing the roadmap for this?

For a parent’s illness — no. For a friend in crisis — no. For a wedding — no. For a fever — no. For a breakup — no. For a genuinely new relationship worth building — no. For “I just don’t feel like it today” — different question. That’s discipline, not life. Refer to 13_discipline/07_motivation_sustainment.md.

The check works because in ten years, the roadmap will be a completed thing (or an abandoned thing) in the past. The people in your life will still be here — or they won’t be. Optimize for the ones who’ll still be here.

The Permission Slip, Again, In Full

Brother —

I’m writing this to you from July 2026, when the plan is fresh and the road ahead is clear. In some future month — maybe month 4, maybe month 9 — something will happen that has nothing to do with inference engineering and everything to do with being a son, a friend, a partner, a human being.

When that moment comes, I want you to remember:

  • You do not owe the roadmap anything. It exists to serve you.

  • Pausing is not failing. It’s honoring what actually matters.

  • The skill will wait. Your parents, your friends, your body, your loves — those don’t wait.

  • The version of you at the finish line who did this with grace, and paused when life asked you to, and came back to it — that person will be a better engineer than the version who ignored a warning to hit an artificial 13-month deadline.

You asked me to help my son. So this is the help: be a son first, an engineer second. Everything else in these 100+ files is downstream of that.

With care, your mentor, best friend, guide.

Escalation Trigger

If you find yourself:

  • Skipping a family event you know you should attend, “because of the roadmap”

  • Missing a friend’s important moment because you were coding

  • Ignoring a health signal you’d tell a friend to see a doctor about

  • Snapping at people you love because “I don’t have time right now”

— stop. Not for a sprint. For a real, honest 3–5 days. Then reassess. You’ve drifted from the plan’s purpose (build a life that supports a great career) to its shadow (a career that consumes a life).

The reset protocol is in 09_summary_and_reset_protocol.md. Read it. Then go call the person you know you should call.

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