3 ms·
That's exactly how I think about "technical debt": it is a marketing buzzword invented by consultants to justify higher rates.
by Tichy 17y ago
That's exactly how I think about "technical debt": it is a marketing buzzword invented by consultants to justify higher rates.
- StrawberryFrog 17y agoI think of it as a geeky buzzword invented by coders to get management to understand the need for refactoring, increasing test coverage, and other necessary "mess-cleanup" actions that revisit working code. In other words, it is a necessary term.
- jerf 17y agoBehind almost every buzzword is a useful concept. "Technical debt" is not one of the exceptions. I have found this useful to keep in mind as I step a bit into the business world. For instance, "solution" and "value proposition" both mean something very important; the fact that many people sling these words around with wild abandon doesn't excuse you from needing to know what they mean. It's the same with "technical debt" and even things like "use case".
- Tichy 17y agoI am not disagreeing in principle, but I have a hard time seeing the value proposition of "technical debt". Doesn't it translate directly to "bad code will cost you in the end, therefore you should hire expensive consultants who know how to code"? I side much more with 37signals (I think it was), who said any code you write will eventually become legacy code. Therefore I wonder if it is really worth fussing so much about the technical debt stuff. On the contrary I have more than once in my dark past as a Java programmer tried to do things "the right way", only to find that a couple of months later "the right way" was just as outdated as everything else.
- mcantor 17y agoThere's a big difference between trying to do things "the right way" and finding out your code still became obsolete, and winging it to produce crappy, unmaintainable code that will cost you hours many times over!