Confront the engineer-specific failure mode of not shipping work that is substantively complete. Define written, external, testable done-ness criteria for the three categories of work you ship. Install a sustainable shipping cadence. Understand perfectionism empirically (Curran's research) rather than as a humble-brag. And actually ship at least one substantive thing during the module — that is the deliverable, and the rest of the curriculum has been preparing the ground for it. Shipping is the deploy. Code that hasn't shipped isn't code that exists — it's a hypothesis. Engineers who would never let unmerged branches rot for months let unshipped features and unpublished drafts rot exactly that way. The discipline is merge-or-close, applied to every category of work. Done-ness criteria are passing tests, not the absence of imaginable improvements. A feature is done when the tests pass and the deploy succeeds — not when no improvement remains conceivable. Engineers who would never block a green build on "I feel like it could be better" block their personal work on exactly that feeling. The criteria document externalizes done; the externalization is the entire fix. The 90% trap is scope creep within a feature — the PR that started as "fix the bug" and became "refactor the module while we're here." Good review culture catches it in code; nobody reviews your personal work, so the criteria document is the reviewer. Name the original scope at the start; reject mid-stream expansion unless consciously re-scoped. And the quality paradox, which Newport and the deploy instinct agree on: you cannot determine what to refactor until you've shipped the first version. The maximizer instinct that wants to ship the perfect version first is, paradoxically, the path to lower quality on a 12-month horizon, because real-world feedback is the only reliable signal for what to improve. Ship to learn what to fix. The ship-to-learn loop beats the prepare-to-ship loop, every measured time.
This course unlocks once you've finished its prerequisite. Open prerequisite →
This is the module where the curriculum finds out whether it has earned its place. Everything before this was preparation — the diagnosis, the body, the evidence base, the habits,…
Procrastination is about not starting. The shipping problem is about not stopping — and it has different etiologies: perfectionism, fear of judgment, scope expansion, the comfort …
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
1. Write DONECRITERIA.md before week 1 begins — for each of your three shipping categories, explicit, testable, external criteria (verifiable by another person looking at the arti…
8 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.