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

Productive vs. Unproductive Work: Measuring Technical Debt

By Frances Lash | September 15, 2014

Definitions of technical debt often revolve around additions made to code ‘sloppily’ (or in the case of this post ‘hackily’) which mount up to difficulty in adding features to the codebase. This post points out that in order to measure the level of the technical debt that has been accumulated  because of  ‘hack’ changes made, ... read more

Managing Technical Debt – Part 1

By Frances Lash | September 10, 2014

Screen Shot 2014-09-09 at 7.49.42 PM
This is a post that gives a good overview of how to manage technical debt by knowing that in order to keep tech debt in check you have to balance time to market and quality. The best run businesses take on technical debt but also set up time to pay it back so that their ... read more

When Code is Considered Technical Debt

By Frances Lash | September 8, 2014

This post tries to explain when code should be considered technical debt, rather than define the term by itself. For example, the post explains that technical debt is often described as code that is difficult to maintain or does not fall under the idea of ‘good code’. The belief that there is technical debt in ... read more

The Law of Brittleness… or Technical Debt?

By Frances Lash | September 6, 2014

There have been many posts that point out problems with the metaphor of technical debt, like the recent post Technical Debt 101: More Speed, Less Haste where the metaphor is dissected. “The Law of Brittleness” does more than explain technical debt but goes as far as to change it’s name.  The term technical debt was an ... read more

Technical Debt, Technical Liability, and Moral Hazard

By Frances Lash | September 4, 2014

Moral hazard is a situation when a party is more likely to take a risk because they are not the ones bearing the possible costs of that risk. This post concludes that one of the sources that can contribute to technical debt is moral hazard – which comes from the person coding being motivated to ... read more

Technical Debt: Do’s and Don’ts

By Frances Lash | September 2, 2014

Atlassian Resource Video.001 copy
This is a kind of ‘wiki-how’ on how to manage technical debt in an agile environment – the right way. Not that there is one right way, but there are a few basics that this article points out. Technical debt, like any other debt should be budgeted in the release and iteration planning. Ultimately, the ... read more