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 | November 17, 2014
Technical debt acts as negative interest on your time that continues to accrue while you work. Here is a post that goes beyond this definition in order to come up with a ‘pay yourself first’ technique to reducing technical debt overtime.
The example of technical debt given in this post is when in one case software ... read more
By Frances Lash | November 12, 2014
Technical debt, as a term, serves to incentivize change within app and portfolio management. However, it fails to translate with business leaders, therefore failing to push through with the change it seeks to promote. In this post, Phil Murphy expands on his love/hate relationship with the term; lauding the “sentiment for change” it inspires, but ... read more
By Frances Lash | November 6, 2014
Technical debt is often treated as an afterthought; teams convince themselves that they have taken into account the extra time and effort required to address tech debt in their planning, making it easy to justify carrying debt for a long time. One way to explain the side effects of carrying on small amounts of technical ... read more
By Frances Lash | November 3, 2014
Technical debt is usually always referred to in a negative sense, whether it be how to avoid it or how to get rid of it. However, here is a post that distinguishes between good and bad technical debt. This post makes the point that in most systems, when graphing their technical debt curve it consistently ... read more
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