Tech debt’s a pain. You’re deep in a codebase, everything feels fragile, and someone eventually says: “should we just rewrite it?”
This post by Benjamin Day, a consultant specializing in software development, hits at why that idea sounds good but usually just trades one mess for another:
https://vslive.com/blogs/news-and-tips/2026/01/the-tech-debt-trap-and-the-rewrite-trap-that-makes-it-worse.aspx
Tl;dr: Rewrites feel clean, until they snowball. You forget weird edge cases. Timelines slip. Now you’ve got two broken things instead of one. Meanwhile, the real issues (i.e., slow dev, low morale, brittle systems) persist.
Worth a read if you’ve ever thought “burn it down” was the answer!