Kill the Rewrite. Ship the Patch.

Six months of refactoring a codebase nobody asked you to touch isn't craftsmanship. It's cowardice dressed as taste.

I spent three weeks in February 2025 rebuilding our notification pipeline from scratch. Greenfield project, no legacy constraints, my choice of stack. By April, the new system was handling forty percent fewer edge cases than the one it replaced. The old code was ugly—nested callbacks six levels deep, magic numbers documented only in depot threads from 2018, a comment in broken English from a contractor who left before anyone learned his last name. But it worked. Every pathological input that broke my clean rewrite? The old pipeline swallowed without complaint.

Ugly Code Is Battle-Tested Code

Legibility is not correctness. Maintenance engineers know every ugly branch is a scar from prod. Delete it, and the wound reopens. The hack you mocked may be the reason the database survived.