Funny thing is that technical debt is not like money debt. There is a lot of possibilities that this debt will just be deleted, obsoleted, project discontinued.
So it is more like survivorship bias, you only get to fix debt that is still alive. Debt that went away and no one is ever paying it is nowhere to be seen.
Bankruptcy is one way to erase debt, and the most horrible debts go out that way.
So it's like survivorship bias, where the most important technical debt (the one that kills its project) is often not noticed.
Re:Using Technical Debt in Your Favor
by endorphone on Thursday March 22, 2018 @10:03AM
(#16648721)
On the flip side, be thoughtful that your job exists because that code was hammered out.
I've created loads of technical debt over my career, in the process literally creating whole product lines that later became the career home for teams of people.
My greatest accomplishment at my current job has been deleting 45K-60K lines of code.
Not every bit of code will be perfect for many reasons, but please be thoughtful at least, and not just hammer out code. Someone else is going to have to clean up your mess.