It's actually velocity debt, not technical debt
There are many kinds of technical velocity debt 1. There are those decisions you, as an engineer, make in the moment to finish a piece of work. Given more time, energy, and space to think, those are decisions you would have made differently. There’s the kind of debt that’s unused code—a retired feature, ignored test specs, multiple implementations of the same helper method or component. Then, there’s the kind of debt that we’ll cover here, debt that isn’t even directly yours, but it impacts you every single day: outdated dependencies. ...