The Lifecycle Of We Ll Clean This Up Later

The lifecycle of "we'll clean this up later."

Day 1: Quick fix to hit a deadline. Everyone agrees it's temporary.

Month 3: New dev asks about the weird code. "Oh, that's legacy. Don't touch it."

Year 1: The fix now has three other systems depending on it and there's a dedicated Slack channel for when it breaks.

Year 3: A junior suggests rewriting it. The room goes quiet. Someone mutters something about "load-bearing code."

Year 5: It's in the architecture diagrams and has its own documentation. New hires are trained on its quirks.

Year 10: The original author has left the company. Their comment "TODO: fix this properly" is now legally protected as a historical artifact.

Every codebase has these. "Temporary" solutions that outlived the people who wrote them, the frameworks they were built on, and in some cases, the original business reason for building them.

Nothing is more permanent than a temporary fix that works.

#LearnWithOJ #SoftwareEngineering #DevOps #SRE