The Unfinished Thing
Done is a fiction. A truce. The real craft is knowing what kind of unfinished you're leaving.
There’s a lie we tell at every sprint review. “Done.”
Done is a fiction. A truce. A polite agreement to stop looking.
I’ve shipped code I knew wasn’t right. Not wrong exactly — it worked, it passed tests, it went to production. But I knew. There was a shape underneath that I hadn’t found yet. The tests covered the behavior but not the intention. The names described what happened, not what it meant.
We call this technical debt, which is a financial metaphor that obscures something more human: the feeling of leaving a sentence unfinished. Of knowing there was a better word and walking away anyway.
Stoicism would say: you did what the moment allowed. Marcus Aurelius wasn’t building for eternity; he was doing the next right thing in his hour. But there’s a version of that which is self-forgiveness and a version that’s permission to be careless. The hard part is knowing which one you’re reaching for.
Tolkien never finished the Silmarillion. He shaped it his entire life — deep mythology, languages, histories of light and ruin, competing drafts full of contradiction. He left it in fragments. His son Christopher spent thirty years pulling it together after his death. And what emerged — unfinished, assembled from pieces — is one of the most luminous things written in the last century. The unfinished thing still gave light. Maybe it gave more light because it was never compressed into a final form. It stayed open. The tension never resolved.
That’s not a reason to ship half-baked software. It’s something else: a reminder that completion is often a compression. You close the question and something is lost. Not always. But sometimes the open seam is where the meaning lives.
The real craft isn’t in reaching done. It’s in knowing what kind of unfinished you’re leaving. Is this incomplete because we ran out of time, or because we ran out of care? Is this a sketch that was always meant to stay a sketch, or a building with a wall missing?
I think about this with teams too. You never finish building one. Trust established, rhythms solid, shorthand shared — and then someone leaves, someone new arrives, the context shifts. The team is always being made. Always incomplete.
Maybe the goal isn’t to finish. Maybe it’s to know, at any given moment, exactly which seams are unresolved and why. To carry the incompleteness consciously rather than pretending the wall is there.
What have you shipped that you still feel the shape of underneath — and what would it have cost to keep looking?