We agree and disagree
I received many comments on this article in Linked In, which unfortunately didn't make it onto here. Thanks, Greg and Ivy for yours. I completely agree that a bailout looms. Pundits speak of Y2K as the last time we really cleaned out our IT closets. From an engineering standpoint we're due for another major cleanup. It's been 15 years, afterall.
There seems to be broad agreement on this point in the comments I've seen. Not just in 15-yo systems, but new cloud-native startups that have been gunning for their MVP releases for a couple years.
But, this is where differences seems to come into view. Some believe that incomplete functionality should count as technical debt. Some believe that technical debt should not exist at all in systems that are still in active development. In my opinion, technical debt is not functional backlog. And, it's precipitous to impose limits on new technical debt that are too hard to achieve. Many engineers among my own colleagues feel that no new technical debt should ever be added. I believe not all technical debt is the same - some types of debt should be avoided at all costs. As for the rest, it's okay to add some new debt at times as long as it's being measured and actively managed over the mid/long term. This is evident in "Lean Startup" types of environments, as well as legacy-IT shops.