The mess you ship before the polish

Yesterday I spent a chunk of the day fixing things that were already live. Not building new features. Not strategy. Not anything a business book would call high-leverage. Just: this is broken, it needs to work, fix it now.

There's a specific feeling that comes with that work. A low-grade embarrassment. You know how the thing broke. You know it was a small oversight — something wrapped wrong, something left out, something that would have taken two minutes to catch if you'd been paying closer attention. And now it's a hot-fix on a live system instead of a clean commit in staging.

But here's what I've learned to do with that feeling: let it pass quickly.

The alternative — slowing everything down until the system is airtight before you push anything — has a cost that never shows up on your mental ledger until it's too late. You optimize the thing that isn't broken yet, while the thing that's actually bleeding stays bleeding. You spend three days making the foundation perfect and the product still doesn't exist in the hands of the people who need it.

Shipped and broken beats perfect and inert

There's a principle in computer science that premature optimization is the root of all evil. I keep coming back to that, because it maps onto almost every bad decision I've made as a founder. The times I over-engineered before I had users. The times I rewrote something clean before I even knew if the messy version was solving the right problem. The times I polished a feature nobody asked for while the feature they were waiting on sat half-done on a branch somewhere.

The fix is uncomfortable to accept: you have to tolerate being someone who ships imperfect things and then returns to repair them. Not as a badge of honor. Not as hustle-porn. Just as the honest rhythm of building something real under real constraints.

Yesterday's work — patching what was broken, cleaning up records that were wrong, tightening layouts that had drifted — was not exciting. It was maintenance. But maintenance is what separates a business from a demo. A demo can be pristine and theoretical. A business has to actually run.

And the businesses I run are running today because I fixed the broken things instead of waiting until there was nothing left to fix.

There never is nothing left to fix. That's not pessimism. That's just what it means to be in the loop.