Refactor Fatigue
ELI5 — The Vibe Check
Refactor fatigue is when your team has refactored the same module four times in a year and nobody wants to touch it again. Every refactor improves things 10%, but the cost of change is piling up and morale is low.
Real Talk
Refactor fatigue describes diminishing returns and team frustration from repeated, incomplete, or conflicting refactoring efforts on the same code. Causes include lack of refactor planning, unclear target architecture, and shifting team priorities. Prevention: commit to one refactor strategy, finish it fully, then stop for a quarter.
When You'll Hear This
"The team has refactor fatigue — this is the fifth attempt at the router." / "Finish the refactor or don't start it. Fatigue kills momentum."
Related Terms
Refactor
Refactoring is cleaning and reorganizing your code without changing what it does — like tidying your room without throwing anything away.
Refactor Tax
Refactor tax is the extra work every feature costs because you're simultaneously refactoring underlying code. Each PR becomes 30% larger and 50% riskier.
Rewrite Syndrome
Rewrite syndrome is the near-universal engineering urge to throw out existing code and start over. 'It would be so much cleaner if we rewrote it in Rust.
Technical Debt
Technical debt is the coding equivalent of putting things on a credit card.