Built is not the same as shipped

Yesterday I crossed a line I had been circling for a few days. Something I had built and tested was sitting there, ready, and I had to make the call to put it in front of the people who needed it.

There is a specific kind of procrastination that looks like diligence. You keep testing. You add one more edge case. You tell yourself it is not ready because this one corner is not handled. The truth is usually simpler: you are afraid of what happens when real people touch it.

"Real artists ship." I have seen that line a hundred times and it always sounded like permission to lower your standards. It is not that. It is a diagnosis. The artist part is the vision. The ship part is the act of committing - of saying this is what I made, now it has to live in the world and not just in my head.

There is a difference between something being done and something being shipped. Done is a state on your machine, in your test environment, in your thinking. Shipped means someone is using it right now, and whatever happens next is real.

The harder move

Yesterday I also retired something. A set of interfaces I had built, maintained, and improved over time. I killed work I had already done and moved everything into a different approach. That was harder than shipping something new. You have to accept that what you built before was a step, not a destination. That is a specific kind of difficulty nobody warns you about.

Solo businesses accumulate half-finished decisions. Things that are built but not deployed. Things that work but are not yet retired. Every one of them is a small weight. Not a crisis. But they compound. Your energy goes into maintaining the in-between state instead of moving forward.

The discipline is not shipping fast. It is shipping at all. Crossing the line from your machine to theirs. Making the call. Retiring the old version. Committing to what comes next.

The thing you built last week is only useful to someone else.