4 ms·

I agree and I can't stand it when people dilute terms to the point they become meaningless. I see it in other areas as well. It isn't a profound thought to tak

I agree and I can't stand it when people dilute terms to the point they become meaningless. I see it in other areas as well. It isn't a profound thought to take a term like "technical debt" and just say well that's just everything. Technical debt is absolutely that, adding something that incurs a level of interest, until you take the time to pay it off. In life, we often always have a level of interest to be paid. It's a good analogy

rjzzleep 3y ago
Almost ten years ago I had the unfortunate opportunity to work with a master manipulator who was unfortunately more senior in the hierarchy. Most of his code was actually technical debt. The code that wasn’t was external code he integrated. All of the code he wrote would eventually break down and until it did world force you to work around it, so it wouldn’t fail from interfacing with it. In one of the standup’s i used the term technical debt to argue for fixing one of these issues that broke later but which he discouraged everyone to fix. After that he integrated the term into his daily use to the point that it became meaningless. The people that believed this snake oil salesman thought that he had already carefully weighed his own decisions in advance. Needless to say the issue was not fixed before he left the company and cost millions and plenty of customer headaches.