4 ms·
I still don’t see a benefit of being vague and call this TD. You can be explicit and explain why things are as they are and if we have to do some extra work be
by louwrentius 5y ago
I still don’t see a benefit of being vague and call this TD.
You can be explicit and explain why things are as they are and if we have to do some extra work because of code addressing no-longer-relevant-use-cases, that’s just it.
No need to call this TD. Be clear and explicit.
I think in most cases, Technical Debt is a much abused term to bullshit and cover up past mistakes. TD sounds much better than mistake and it sounds so ‘inevitable’, so you can’t be blamed.
- andrewingram 5y agoI don't disagree, I have no real attachment to the term and I think there's too much nitpicking about what the precise definition is. At the end of the day, sometimes past work can slow down present and future work; and if the impact is significant, you should do something about it.