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

Technical Debt: A Framework for Product Managers

By Frances Lash | March 26, 2015

Here is a post that discusses why and how product managers must access and manage technical debt. Technical debt often first considered as solely theory, until the pressures of time and customer desires create the need for compromise and quick and dirty shortcuts. Once the results of these pressures start to build up and create ... read more

Technical Debt – It Is Not Inevitable

By Frances Lash | March 25, 2015

Screen Shot 2015-03-24 at 11.46.42 PM
This post beings with an interesting statement: that in a start up environment technical debt often feels inevitable. Technical debt can be seen as a function of moving fast, minimum variable products (MVP), prototypes, agile practices, and of releasing the product to market as soon as possible. The idea of using a minimum variable product to ... read more

Technical Debt: What It Is, and What It Means for Your Web Project

By Frances Lash | March 23, 2015

Screen Shot 2015-03-23 at 7.14.53 PM
If any piece of software is seen as an investment for your business than it is best to not think about driving costs down to a base minimum. It is better to focus on the return that the money and time invested can generate. This sort of financial metaphor is helpful to understanding technical debt. ... read more

Technical Embezzlement: Technical Debt Without Agreement

By Frances Lash | March 17, 2015

This post describes a new term related to technical debt: technical embezzlement. In order to further define the term, building off of technical debt is necessary. Technical debt refers to the eventual consequences of poor system design, architecture, or development in a codebase. If this debt is not repaid it begins to accumulate interest and ... read more

Technical Debt: A Repayment Plan

By Frances Lash | March 13, 2015

Screen Shot 2015-03-12 at 1.59.38 PM
Technical debt is usually incurred when a team consciously makes the decision to put in less than optimal technical work for the short term gain of their project. For example, the team may not put in depth automated tests into their code in order to get the product to market sooner. The key to technical ... read more

Is Tracking Technical Debt A Waste Of Time?

By Frances Lash | February 26, 2015

mh_dzone_logo
Tracking technical debt in the development backlog is meant to make the costs and risks of the technical debt taken on visible; prioritizing debt payments with other work is supposed to ensure that the payments get made. This post argues that tracking debt is not worth it. These are the reasons listed: Some code often isn’t worth ... read more