4 ms·
> For instance they will insist that code that was just written fresh by a colleague is "tech debt" because they would personally have written it differently, w
by mcv 8y ago
> For instance they will insist that code that was just written fresh by a colleague is "tech debt" because they would personally have written it differently, when there are no meaningful differences between the two approaches.
> They can claim that a design they don't understand the reasons for immediately (regardless of whether it's documented) is tech debt.
> They can claim any feature they don't personally want to do or which is perceived as hard work will create tech debt. And so on.
Yeah, those things are not technical debt. But that doesn't mean that technical debt is a real issue. Technical debt isn't about whether you like or understand a particular approach, it's about whether the codebase as a whole is still maintainable, whether the bugs make sense and are fixable, whether new features can be added without stabilising the whole code base.
It's never the new feature that's the problem. If the new feature can't be added in a good way, it's the old codebase that has unhandled technical debt.
- 0xdeadbeefbabe 8y agoUgh. Instead of redefining common usage you could just use a different word or words. Edit: Is saying "bad design" or "ineffective design" going to lead to some fearful confrontation?
- geezerjay 8y agoOP's usage and explanation of the term are spot on, and you miss the whole point if you conflate technical debt with bad design. One of the causes of technical debt is a change in requirements, and changing the initial requirements doesn't mean that the design was bad.
- 0xdeadbeefbabe 8y agoCommon usage misses the whole point as well.
- geezerjay 8y agoJust because you personally misundertand a concept it doesn't mean everyone else is wrong.
- 0xdeadbeefbabe 8y ago> I think a lot of the time when a developer shouts “technical debt” what they are really shouting is “code someone else wrote that I’d rather rewrite than understand”. Is it obvious to you that it's not just me?
- jibal 8y agoWhat common usage was redefined? Where would you substitute "bad design" or "ineffective design" into the comment? Perhaps this will help: http://wiki.c2.com/?TechnicalDebt http://wiki.c2.com/?TechnicalDebt
- 0xdeadbeefbabe 8y agoCommon usage is "I'd rather rewrite than understand the problem", as well as "I disagree with decisions that were made." > Perhaps this will help: http://wiki.c2.com/?TechnicalDebt http://wiki.c2.com/?TechnicalDebt Seriously, it won't. That's the point. People overload these words. It's a cute ideal definition though.
- jibal 8y agoYou are so full of dead beef. You wrote "Instead of redefining common usage you could just use a different word or words", but he used the word as correctly defined. It's a pity that you aren't helped by knowing what the word means, but that's your problem, and the consequence is that sensible people write you off as a silly troll. Over and out. P.S. Yeah, go ahead and downvote me, troll.
- deleted 8y ago[deleted]
- 0xdeadbeefbabe 8y agoHey it's nothing personal. I'd apologize for trollishness, but I really believe what I'm saying. Edit: I apologize for beating a dead horse.
- jibal 8y ago> Technical debt isn't about whether you like or understand a particular approach, it's about whether the codebase as a whole is still maintainable, whether the bugs make sense and are fixable, whether new features can be added without stabilising the whole code base. It's not about that either ... it's about things that were put off, generally for valid reasons at the time. > It's never the new feature that's the problem. What do you mean by "problem"? Many new features are inherently problematic. > If the new feature can't be added in a good way, it's the old codebase that has unhandled technical debt. That would only apply to waterfall development with infinite foresight. In the real world, wise people employ the YAGNI principle.