We’ll Fix It Later: Famous Last Words in Software
“We’ll fix it later.”
It sounds harmless. Practical, even. When deadlines are tight and priorities are shifting, pushing something down the road feels like the right call.
But in software, “later” has a way of becoming never — or worse, much more expensive.
Small Shortcuts Don’t Stay Small
Skipping documentation. Hardcoding a value “just for now.” Putting off proper error handling.
Individually, these decisions seem minor. But over time, they stack up.
What starts as a quick shortcut becomes part of the system’s foundation — and now it has to be worked around instead of fixed.
Technical Debt Compounds
Every “we’ll fix it later” decision adds technical debt.
And like financial debt, it accrues interest:
Changes take longer
Bugs become harder to track down
New features introduce new problems
Confidence in the system drops
Eventually, even simple updates feel risky.
Later Is Always More Expensive
Fixing something early is usually straightforward.
Fixing it later means:
Untangling dependencies
Reworking existing functionality
Testing across multiple scenarios
Potential downtime or disruption
The longer an issue sits, the more it costs — in both time and money.
It Becomes “Too Big to Fix”
At some point, the list of things to “fix later” becomes so large that no one wants to touch it.
So it stays.
And the team adapts:
Workarounds become normal
Inefficiencies are accepted
Problems are avoided instead of solved
The system still runs — but it’s no longer working for the business.
Final Thought
“We’ll fix it later” isn’t a plan — it’s a delay. And delays in software don’t eliminate work. They multiply it.
The best time to fix something is when you first notice it. The second-best time is before it becomes a problem. Anything after that gets expensive.