The Stride Blog
Get the latest tips on agile software development so you can scale and embrace change.
Technical debt has become a ubiquitous metaphor in the world of software development. If you're not familiar with it, the gist is that it represents the accumulation of design errors you've made, shortcuts you've taken while trying to meet a deadline, and perhaps even the inconsistent domain language and code/architecture styles you have living side by side in your code base that slow down development, cause confusion in meetings, or make it harder to onboard new developers. Basically the sum total of everything that's wrong with your software in various ways from how you'd like it to be if you were starting over clean today to write something that did exactly the same thing. Every organization I've encountered acknowledges that it has some debt, but none of them seem to take the metaphor very seriously.