Eric Allman
Skip Abstract Section
Abstract
In 1992, Ward Cunningham published a report at OOPSLA (Object-oriented Programming, Systems, Languages, and Applications) in which he proposed the concept of technical debt. He defines it in terms of immature code: "Shipping first-time code is like going into debt." Technical debt isn’t limited to first-time code, however. There are many ways and reasons (not all bad) to take on technical debt.
- Brooks, F. 1995. The Mythical Man-Month, Anniversary Edition. Chapter 11. Addison-Wesley.Google Scholar
- Cunningham, W. 1992. The WyCash portfolio management system. OOPSLA Experience Report;http://c2.com/doc/oopsla92.html. Google ScholarDigital Library
- Fowler, M. 2009. Technical debt quadrant; http://martinfowler.com/bliki/TechnicalDebtQuadrant.html.Google Scholar
- Freeman, S. 2010. Bad code isn't technical debt, it's an unhedged call option. Higher-order Logic;http://www.higherorderlogic.com/2010/07/bad-code-isnt-technical-debt-its-an-unhedged-calloption/.Google Scholar
- Grossman, S. 2011. Calmail crashes last multiple days. The Daily Californian (December 1); http://www.dailycal.org/2011/12/01/calmail-crashes-last-multiple-days/.Google Scholar
- McConnell, S. 2007. Technical Debt. Construx Conversations: Software Best Practices; http://blogs.construx.com/blogs/stevemcc/archive/2007/11/01/technical-debt-2.aspx.Google Scholar
Index Terms
- Managing Technical Debt: Shortcuts that save money and time today can cost you down the road.
Index terms have been assigned to the content through auto-classification.
Recommendations
Ninth International Workshop on Managing Technical Debt: report on the MTD 2017 workshop
XP '17: Proceedings of the XP2017 Scientific WorkshopsWelcome to the Ninth International Workshop on Managing Technical Debt, collocated with the 18th International Conference on Agile Software Development (XP 2017) in Cologne. The technical debt research community continues to expand through ...
Comments