The fix that wasn't finished

There is a specific feeling when you re-open something you already fixed and find that it's still broken. Not broken the same way — broken differently, in a way that only exists because you touched it.

I traced one yesterday. A rule had been changed so that more items appeared in a selection list — the visible symptom was gone, the ticket looked closed. But the code that ran when you actually made a selection still enforced the old rule. The result: you could see the option, click it, and get told it wasn't eligible. The half-fix was worse than the original problem, because at least before, the right things were simply hidden. Now they were visible and broken, and the user had to figure out why.

The mistake is calling it done when the symptom disappears, instead of when the system is coherent.

The shadow every fix casts

Every fix has a surface — the visible part you changed — and a shadow: the places where the old behavior still lives. The discipline isn't just shipping. It's tracing. You don't get to call something done until you've found the shadow and dealt with it.

Every business has this shape, not just in software. A customer complains, you address it for them, you move on. But the thing that caused the complaint is still live in three other places — your returns policy says one thing, the email template says another, the person answering the phone says a third. You haven't fixed the problem. You've added a layer of inconsistency on top of it. Now the customer gets two different answers and has to figure out which one to believe.

Real artists ship is true. Waiting for perfect is how good work gets buried. But there's a version of shipping that just moves the problem downstream, makes it slightly harder to find, and hands it to the user to discover. That isn't shipping. That's offloading.

The question I try to ask before closing anything: where else does this logic live? Usually there's at least one more place. Yesterday it was three separate spots, all carrying a rule that had been updated in one but not the others.

The first fix is rarely the finish. The first fix is just proof you found the problem. Finishing means following it all the way through.