Pre-Mortem 09 — Summary & Reset Protocol

The eight files before this one named the ways this plan can fail. This one names how you get back up.

The Eight Failure Modes At A Glance

#

Failure Mode

Probability

Primary Parry

Escalation Trigger

01

Industry moves faster than roadmap

~40%

Quarterly re-scan; principles over primitives

2+ files in one phase go stale in a quarter

02

Zoho time starvation

~70%

Zoho-alignment (see 06_zoho_alignment.md); non-negotiable 2×2h weekday + weekend blocks

Two sprints in a row miss deliverables due to work

03

Burnout, months 6–8

~60%

Discipline files 07 & 08; quarterly week-off; community

You dread opening the laptop 3 days in a row

04

Shiny object syndrome

~50%

Sprint contract; the “one true north” card; 3-strike rule

You’ve context-switched twice mid-sprint

05

Open source political blockage

~30%

Portfolio triangulation across vLLM/SGLang/FlashInfer/llama.cpp

A PR sits >6 weeks with no maintainer response

06

Hardware access choke

~35%

Local 3090/4090 as primary; rent H100 only for specific runs

You’ve spent >$200/month without a shippable artifact

07

Geography / visa / offer conversion

~55%

Three-track application (Zoho / Indian / Remote-intl); 15–18mo conversion window

M11 = zero study loops open

08

Family, health, life

~85%

Permission slip; the ten-year regret check; life comes first

You’re skipping people you love “because of the roadmap”

Notice: Failure 08 is the highest probability by a large margin. The other seven you can engineer around. That one you honor.

The Composite Risk Picture

The critical thing this diagram shows: the reset is a loop, not an exit. You can hit it multiple times. The roadmap doesn’t end at reset; it re-enters the loop.

The Reset Protocol

When something has gone wrong — you missed two sprints, or you’re burnt out, or life came for you, or an entire phase went stale — here is what you do. In this order. No skipping.

Step 1 — Stop. Actually Stop.

Do not “try harder.” Do not “just push through one more sprint.” Both are the exact reactions that turn a two-week problem into a two-month problem.

Close the laptop. Take 48 hours minimum with zero roadmap contact. Sleep. Walk. Eat something cooked by someone who loves you. Talk to a person who is not on the internet.

Step 2 — Diagnose

Open 99_pre_mortem/ and read the eight failure-mode files. Ask honestly: which one is this? Usually it’s one of them, sometimes two overlapping. The diagnosis matters because each has a different parry.

Write down, in one sentence, what happened:

“Sprint 12 slipped because [Zoho quarterly release] pulled me for three weeks, and when I came back I couldn’t remember where I was in the FA2 implementation, so I opened Twitter instead of the codebase.”

That sentence — honest, specific, blameless — is worth more than any recovery plan.

Step 3 — Repair

Apply the parry from the relevant file:

  • Time starvation (02) → renegotiate the Zoho quarter; if impossible, extend the roadmap by the number of weeks you lost. Do not compress the missed content into a smaller window.

  • Burnout (03) → mandatory one-week off. Not “light week.” Off. Then start the next sprint at 60% intensity for two weeks.

  • Shiny object (04) → close the tabs. Return to the sprint contract. Log the shiny thing in a “future work” file so your brain lets go of it.

  • Political blockage (05) → change the target project. Do not sit and wait.

  • Hardware choke (06) → downshift to what your 3090 can run; the fundamentals don’t need H100s.

  • Geography (07) → begin the three-track application earlier than planned. studies are also a form of learning.

  • Life (08) → drop everything. Go. Log the pause. Come back when you come back.

  • Industry moved (01) → this is actually good news. Read the new thing, update the affected files, resume.

Step 4 — Reset the Sprint Counter, Not the Roadmap

Here is the rule that saves everything:

The sprint counter can restart. The roadmap continues.

If you were on Sprint 12 and slipped, don’t say “I failed Sprint 12 and Sprint 13.” Say “Sprint 12 is now the sprint that starts today, and everything after re-indexes.” You lose calendar time, not roadmap progress. The eight portfolio rungs and seven phases are unchanged; the dates around them slide.

This is not cheating. This is how any professional shipping schedule handles slippage. Read the postmortem template any big engineering org uses — that’s the register we’re operating in.

Step 5 — Log It

Add a paragraph to your lab notebook:

Reset — <date>
Failure mode: <one of 01-08>
What happened: <one sentence, blameless>
What I did about it: <one sentence>
What I'm changing so it doesn't happen the same way twice: <one sentence>
New sprint number: <n>
New M13 target date: <yyyy-mm-dd>

Five lines. That’s the reset log. Don’t make it more elaborate.

Step 6 — Resume

The next Monday morning, at your normal start time, open the codebase and take one small action. Not “make up for lost time.” Not “big push weekend.” One small action. Read one file. Fix one bug. Write one lab-notebook entry.

Momentum returns through action, not intention. This is the whole trick.

The Three Truths To Read On A Bad Day

Sometimes you’ll open this file at 11pm on a bad Wednesday. Here are the three things that are true even then.

1. This plan is a construct. You are not.

The 13-month calendar exists because you named it. You can rename it. You can extend it. You can pause it. It does not have a life of its own; it has the life you give it. When you stop working on it, it stops. When you resume, it resumes. You are the process, not the artifact.

2. The skill is career-long. The plan is not.

Every fear you have about “falling behind” collapses if you zoom out to a five-year timeline. In 2031, will you regret that you took month 7 off to be with your family? No. Will you regret not being an inference engineer by then? Only if you gave up entirely. The difference between finishing in month 13 and finishing in month 18 is zero on any timescale that matters.

3. You are not doing this alone, even when it feels like it.

The GPU MODE Discord has thousands of people at every stage of this journey. r/LocalLLaMA has your peers debugging the same Q4_K_M issues at 2am. The vLLM Slack has maintainers who remember what it felt like to be new. Zoho has colleagues who would be excited about what you’re building if you told them. Your family has people who are proud of you for trying. Isolation is a lie your tired brain tells you. It is not a fact about your situation.

Re-read 03_burnout_month_6_to_8.md §”Community as parry” if this needs reinforcing.

The One Sentence

If this file gets long — and it did — here is the single sentence to remember:

The roadmap serves you. You do not serve the roadmap.

Everything else — the sprints, the KPIs, the rungs, the portfolio ladder, the study timeline, the Zoho alignment plays, the CUDA papers, the FA4 findings, the discipline files, the 100+ md files in this fortress — is in service of your becoming an inference engineer while remaining a whole human being.

If any file, at any point, feels like it’s asking you to sacrifice the second for the first, that file is wrong and you should ignore it until you can rewrite it.

I wrote these files for you. You get to override them.

The Loop Closes

You started this journey by asking me to help my son. This file is the last page of the pre-mortem. Every failure mode is named. Every parry is written. The reset protocol is above.

The rest is not about the roadmap. It’s about who you become while walking it. Be kind to that person. Give him rest, food, family, love, and one hard problem to chew on every day. He’ll do the rest.

Now go build something.

Return to README.md · Back to master ../00_command/README.md