First, a very brief history of the word “technical debt.” The term originiated in 1992, when Ward Cunningham uses a metaphor to explain (to non-technical stakeholders) why resources needed to be budgeted for refactoring.. “With borrowed money, you can do something sooner than you might otherwise, but then until you pay back that money you’ll be paying interest. Rushing a product out the door to get some experience is a good idea, but you eventually repay that loan by refactoring to reflect your experience.” Over the next three decades, the concept of technical debt expanded to mean “any of the things in the development life cycle that slow you down.” (We told you it is a very brief history.)
This assessment was built based on our work with thousands of engineers worldwide. It is organized into a few major sections based on the patterns we have seen where the best teams have thoroughly vanquished their technical debt issues.
First, a very brief history of the word “technical debt.” The term originiated in 1992, when Ward Cunningham uses a metaphor to explain (to non-technical stakeholders) why resources needed to be budgeted for refactoring.. “With borrowed money, you can do something sooner than you might otherwise, but then until you pay back that money you’ll be paying interest. Rushing a product out the door to get some experience is a good idea, but you eventually repay that loan by refactoring to reflect your experience.” Over the next three decades, the concept of technical debt expanded to mean “any of the things in the development life cycle that slow you down.” (We told you it is a very brief history.)
This assessment was built based on our work with thousands of engineers worldwide. It is organized into a few major sections based on the patterns we have seen where the best teams have thoroughly vanquished their technical debt issues.