The Technical Debt Community

So you’ve got Technical debt… now what? Ward Cunningham coined the metaphor back in 1992, and it has since been taken on by the industry to describe the consequences of poor software architecture and bad coding. This website encourages a pragmatic view of technical debt, attempting to elevate the discussion from merely defining technical debt to finding approaches for business technology organizations to use technical debt awareness as a vehicle to fix fundamental problems

Recent blogs posts

Move Fast, Minimize Technical Debt

By Frances Lash | December 17, 2014

This is post with some tips for start-ups to minimize their technical debt. First, it needs to be decided which code is going to be kept. Start-ups will often make code that is temporary and some code that will definitely be around later. Therefore, when code needs to switch from temporary to sustainable the developer ... read more

Inheriting Bad Code: How to Fix and Prevent it

By Frances Lash | December 16, 2014

In this presentation by Kimber Lockhart, as part of the Hack Summit (the virtual conference for programers), she discusses what to do once you’ve inherited bad code. She speaks less about the source of bad code (low budget, high pressure to meet deadlines, company’s decision to hire poor developers) and more on the steps to ... read more

Economics of Quality: Technical Liability and Self-insuring Software – A CISQ Presentation

By Frances Lash | December 3, 2014

Screen Shot 2014-10-22 at 10.26.31 PM
CISQ is the Consortium for IT Software Quality, a special interest group of the Object Management Group organized to create standards for measuring software quality, including the definition of technical debt and factors that influence it: security, performance, reliability, and maintainability.  In this presentation from CISQ, by Murray Cantor senior consultant at the Cutter Consortium, the ... read more

Technical Debt: What it is and why should you care?

By Frances Lash | December 1, 2014

Screen Shot 2014-11-28 at 11.13.17 PM
Technical debt is often directly responsible for many problems that occur when building high quality software quickly – especially as companies move towards more agile methodologies. Technical debt is generally the sacrifice of quality for speed, so when cutting corners to meet a deadline you are accruing technical debt . This debt taken on was ... read more

Technical Debt – What Can You Do

By Frances Lash | November 28, 2014

It is often suggested that businesses seek to create minimal viable products. In other words, to only develop the most important core features that allow for the prompt delivery of a product making time to market the most important factor in product development. The inherent problem with this approach is that there has been a ... read more

Why is Programming so Hard? – Incidental and Accidental Complexity

By Frances Lash | November 25, 2014

Accidental complexity can be referred to as technical debt or sometimes spoken about as incidental complexity – ultimately there is a difference between conscious and unconscious sources of poor code. If it is deliberately decided to deliver suboptimal products, there is a perceived hurry to ship to market. If there is a strong enough incentive ... read more