Software Debt & Design Debt Overview
Join the Technical Debt bloggers in discussions about their thoughts on Software Debt, its impact on code and on the business. If you are interested in blogging for us, let us know!
By Frances Lash | October 30, 2014
Most know the term technical debt in the way that it slows down development and can cause architectural problems, however, this post does well in pointing out other manifestations of the term that also need to be considered under the umbrella of tech debt.
Dead Code, for example, should be considered a form of debt. When ... read more
By Frances Lash | October 29, 2014
CIOs often feel that the rest of their business doesn’t understand the constraints that they are working with, as they are asked to do more when only one fifth of their IT budgets are available for transformation. Here the concept of technical debt can be harnessed by the CIO to highlight issues facing them and ... read more
By Frances Lash | October 23, 2014
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.
A few months ago the Consortium for IT Software Quality (CISQ) had a presentation on ... read more
By Frances Lash | October 16, 2014
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
By Frances Lash | October 14, 2014
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
By Frances Lash | September 26, 2014
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
By Frances Lash | September 24, 2014
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
By Frances Lash | September 19, 2014
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
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
By Frances Lash | September 10, 2014
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