Interesting article. I’m currently trying to justify “tech debt” to upper management. The way I try to communicate it: we can move faster and better on business requirements if we delete unused code/upgrade legacy dependencies/etc. Both need to happen at the same time, though, and that’s where it gets hard: “this feature request would be so much easier if I upgraded to Angular vlatest” runs the risk of always paying tech debt and never providing value.