Your point is one well worth making..."technical debt" is not an inept choice of terms in IMHO... I've been in the trade for decades now...I'm more inclined to

Your point is one well worth making..."technical debt" is not an inept choice of terms in IMHO... I've been in the trade for decades now...I'm more inclined to apply the term "technical baggage" to the feeling I often have these days when sitting down to solve a problem for a client... Layers upon layers of dependencies to sort to do a proper job of putting systems back on sound footing...multiple patches to be examined, some to be discarded...with the clock ticking...non-tech managers love to hear you say, "OK, you're back up"...increasingly, that's what we settle for... All to keep the wheels of commerce turning with as little down time as possible... I have to admit that my discomfort is at least somewhat influenced by comparing the current environment to the environment of the early days...essentially stand-alone programs, elegantly written, performing the same basic function that now require five, ten... Forgive the reminiscence...times are different...