The broken thing that looked finished

Yesterday I spent most of the day not building anything new. I spent it going back.

A rule placed in the wrong position — technically present, functionally useless. Dead code that looked alive. A function that returned success while quietly deleting things it wasn't supposed to touch. A check that fired after the decision it was meant to guard.

None of these were visible unless you went looking. Logs were clean. Pages loaded. Jobs completed and reported fine. If I hadn't carved out time to audit, I'd have kept building new things on top of a foundation with invisible cracks.

This is a particular kind of failure — not dramatic, not obvious, not the kind that lights up a dashboard. It's the thing that "worked" until it didn't. The safety net with a hole you only find when you fall through it. The silent delete that only fires under a condition you haven't hit yet.

The Jobs line gets invoked as an argument against perfectionism: just ship, stop polishing, done is better than perfect. That's true. But there's a counterpart nobody says out loud: once you ship it, it isn't done. It's running in conditions you didn't fully model. It will find edge cases you didn't think of. And it will fail quietly if you let it.

Real artists ship. But they also go back and look.

One thing I found yesterday had been sitting there for months. Not broken in any visible way — a rule in the wrong position, a check that fired after the decision was already made. Technically in place. Functionally pointless. I probably shipped it with confidence.

I've stopped feeling bad about finding things like this. Finding them is the point. The only failure worth losing sleep over is the one a customer finds first.

When you run your own thing, nobody's job is to go back and verify. You have to protect that time deliberately — name it, schedule it, defend it when newer problems crowd in. And resist the urge to measure it against real work. Finding a silent failure is real work. Removing a landmine before it fires is real work. Checking that the thing you trust actually does what you think it does is real work.

It doesn't feel like shipping.

It is.