The mess you ship into

Yesterday I shipped more than I should have been able to. Not because I'm fast — I'm not, particularly — but because I stopped waiting for the conditions to be right and just started moving.

Somewhere in the middle of it I found a fire I hadn't set. An automated system I'd disabled weeks ago had been running anyway, quietly doing damage in the background. Messages going out, queues building, devices logging out. The kind of thing that only surfaces when you're already neck-deep in something else.

The old version of me would have taken that as evidence that I shouldn't have shipped anything yet. That the foundation was too shaky. That I needed to audit everything before adding anything new.

But that's not how it works. You don't find the fire by standing still. You find it by turning the lights on — and you turn the lights on by building something that requires them.

Shipping is the diagnostic tool

There's a version of perfectionism that disguises itself as responsibility. It sounds like: I just want to make sure it's solid before I put it in front of anyone. What it actually is: a way to stay in control by staying invisible.

The mess I found yesterday — the runaway queue, the edge cases, the identifier that couldn't be decoded the way I'd assumed — none of that would have appeared in a planning document. It only appeared because something real was running and real things were happening inside it.

Steve Jobs said real artists ship. Most people hear that as a push toward boldness, a permission slip. I think it's actually a statement about epistemology. You don't fully know what you've built until it's out. The shipping is the knowing.

That's uncomfortable if you're the kind of person who wants to understand something before you release it. But the loop only closes in one direction. Build → ship → learn → build again. There is no shortcut that goes build → understand → ship → nothing breaks.

I fixed the fire. I built a gate so it couldn't happen again. Then I kept building.

Not because I was fearless. Because the cost of not knowing was higher than the cost of finding out.

The work that scares you into waiting is usually the exact work that needs to go out first.