4 ms·
Perhaps what he's saying is that folks use the term "technical debt" as a fancy way of getting away with writing crappy code. When in fact technical debt is the
by DanielBMarkham 17y ago
Perhaps what he's saying is that folks use the term "technical debt" as a fancy way of getting away with writing crappy code. When in fact technical debt is the stuff you couldn't have avoided if you wanted to, because you didn't know then what you know now.
Ok, I'll buy that. But to me, from an external point of view, my developers have all this extra work to do which doesn't have to do with their backlog. So who cares what the term they use is?
I think he's just mad at sloppy coders co-opting a favorite term. I see so much muddled language it doesn't really bother me. As one other poster noted, it's not like when you coin a term you get to define what the term means for the lifetime of the universe.
- prodigal_erik 17y ago> technical debt is the stuff you couldn't have avoided if you wanted to, because you didn't know then what you know now. I've always understood it as just the opposite: the circumstances don't permit doing it right, so you do it badly knowing it'll cause problems, and the costs grow the longer you leave it unresolved. Debt is a metaphor for choosing to sacrifice your future self's resources, not just making mistaeks (even if they have the same result).
- DanielBMarkham 17y agoMe too. That's the way the term is commonly used. But if I understand this author correctly, that's not what the term originally meant.
- prodigal_erik 17y agoNow that I reread it, "[...] code that is clean enough to be able to refactor as you come to understand your problem" is a strange statement. Isn't refactoring just producing a cleaner version of the same solution?