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

Faster Software Development with (Smart) Technical Debt

By Frances Lash | October 16, 2014

Screen Shot 2014-10-15 at 10.19.43 PM
Technical debt often arouses bad associations in developers’ minds because so often when the term is brought up, it is almost always a bad thing. Here is a post that presents an argument for using technical debt as a business tool and the steps that must be taken to use it as thus. Much of ... read more

Managing Technical Debt with Agile: Care About Your Code

By Frances Lash | October 14, 2014

Screen Shot 2014-10-13 at 10.32.00 PM
Managing technical debt is easiest when there is an outline to help your development team discuss how classify and prevent technical debt. This post does just that. Technical debt is classified in several ways according to Martin Fowler’s tech debt quadrant (prudent and deliberate debt; reckless and deliberate debt; reckless and inadvertent debt; prudent and ... read more

Technical Debt: Avoiding Loan Default

By Frances Lash | September 26, 2014

Screen Shot 2014-09-26 at 5.38.14 PM
Here is a straightforward post on the contributing factors of technical debt. A list of ways in which technical debt usually accumulates includes: business pressures (when meeting deadlines becomes more important than completing remaining tasks), not constructing code flexibly, lack of unit testing, and lack of shared knowledge between team members. From here it can ... read more

Paying Down Technical Debt: Work Smarter Not Harder

By Frances Lash | September 24, 2014

Screen Shot 2014-09-24 at 12.02.26 AM
This post starts off with an illuminating comparison: between IT shops that work strenuously trying to complete 2 weeks worth of work in 6 days and achieve very little, and other organizations that seem to make much more progress in their work with less hours. The idea of working smarter – not harder – comes ... read more

Using Agile Techniques to Pay Back Technical Debt

By Frances Lash | September 19, 2014

ee819135.Laribee_Figure1(en-us,MSDN.10)
Acknowledging that some form of technical debt exists in every codebase is paramount to managing debt and staying in “the black”. Asides from the fact that technical debt kills productivity thus leading to economic downsides, there exists a psychological downside to technical debt. If a developer dreads dealing with code that is brittle and filled ... read more

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