A café was closing in an hour. The work in front of us — pulling a payments-and-signatures service out of a Rails app it had quietly outgrown — was nowhere near done.
We stopped anyway. Nothing was lost.
Not because the work was finished. Because of a rule we had written down an hour earlier: no multi-step build starts until there is a checklist that anyone — the next person, the next session, the next model — can pick up cold.
The rule that sounds like more work
Here is the convention, in full: before writing implementation code for any multi-step build, migration, or refactor, you produce a written execution roadmap and commit it to a tracked file. Not a sticky note. Not a thread in someone’s head. A file, in the repository, that the next set of hands can read and continue from. We added it to the top of our operating manual as a hard prerequisite, not a nicety.
Read cold, it sounds like bureaucracy. It sounds like the opposite of doing nothing — one more document to maintain before you are allowed to do the real thing.
It is the opposite of the opposite. The checklist is the precondition for rest.
What we were actually afraid of
The thing that keeps you chained to a build is rarely the unfinished work. It is that the plan lives in exactly one place: a single person’s short-term memory. They cannot step away — not for a weekend, not for a closing café, sometimes not for dinner — because only they know what comes next, which step is half-done, which decision is still load-bearing.
That person is not a hero. That person is a single point of failure who happens to be tired.
A checklist that lives in someone’s head is not a checklist. It is a hostage situation, and the hostage is the project.
What a resumable checklist actually contains
Three parts, and the third is the one that matters most:
A pre-flight checklist — the access, credentials, and decisions you confirm before writing code, so the build does not stall halfway on a missing key or an un-made call.
A sequenced plan — the work broken into ordered units, each one small enough to ship and verify on its own.
A resume tracker — a status line per unit and, at the very top, a plain RESUME HERE marker pointing at the first thing that is not done.
The marker is the whole trick. It is one line that says start here, so the next person does not have to reconstruct the state of the world before they can move. They read the marker. They continue.
Our worked example is public: the plan to extract that payments service opens with a RESUME HERE banner, lists the work as a sequence of small pull requests, and tracks which have merged. When the café closed, the marker pointed at the first step. That is exactly where the work will pick up — whether the next session is a human or a model, tomorrow or next week.
Why this is the most Do-Nothing thing we do
We have written before about letting the machines run the chain and letting humans hold the soul — automating the deploys, the ledger entries, the reminders, everything a finite state machine can carry, so that people are freed for the things only people can do.
The checklist is the quiet mechanism that makes that division survivable. When the plan is written down and tracked, the thread stops depending on anyone staying awake. The machine holds the place in line. The human gets to leave the building.
Doing nothing was never about idleness. It is about refusing to be the part of the system that breaks when you go to sleep.
Where the soul comes back in
A checklist cannot decide whether the thing is worth building. It cannot read the room, taste the chocolate, sense that the story has shifted, or notice that the project everyone agreed on last month is quietly the wrong one now. Those are the parts no marker can resume.
So that is what the human keeps. The checklist holds the where. The person holds the why — the judgment, the attunement, the decision to keep going or to stop. Everything else — the order of steps, the state of the build, the next move — is overhead. Write it down, and walk away from it on purpose.
The café closed
The laptop closed with it. The plan stayed open — on a tracked file, with a marker pointing at the next step, available to whoever or whatever picks it up next.
Let the machine hold the place in line. Let the human hold the why.
Join the discussion
Share your thoughts in Telegram, Beer Hall, and on the DAO web app.