Nobody tells you when something breaks

Yesterday I found out that a contact form on one of the businesses I run has been broken since April. Six months. Not broken in a dramatic way - no errors, no crashes. Broken in the way that looks fine from the outside: the form was there, it accepted input, and every submission went exactly nowhere.

In a company with a support queue and a monitoring dashboard, someone catches this in a week. In a one-person operation, you catch it when you finally decide to look.

That's the tax nobody names. Not the failures that blow up loud enough to pull you away from whatever you were doing. Those are survivable - they're urgent, they're visible, and urgency creates clarity. The harder thing is the quiet decay. The page that looks alive but isn't. The process that ran its last real cycle months ago and has been going through the motions since. Nobody files a ticket for this. It just sits there.

The energy goes forward, not backward

Shipping is celebrated. Maintenance is not. Every launch is a moment. Everything you've already launched becomes background noise. The pull is always forward, which means the things behind you deteriorate on their own timeline, not yours.

Reid Hoffman's line about embarrassment and timing is right - but it's advice for what you're about to ship. The embarrassment I felt yesterday was about something I shipped in the spring and then stopped watching. That's a different kind of mistake. Less perfectionism, more attention.

When I finally rebuilt it, I built it properly. Better than the original. The kind of work you do when months of real-world context tells you exactly what the first version needed and didn't have. So the gap wasn't entirely wasted. But a gap is a gap.

What I keep coming back to: the work that matters isn't always the work in front of you. Sometimes it's the thing you shipped and walked away from. The discipline isn't only in the launch. It's in remembering to turn around.

Most things are still standing when you do.

Not this one.