Internal Software Quality & Messy Code

Internal Software Quality and Technical Debt are two concepts that are tightly linked: if we can measure the technical quality in our messy code, we can then start to measure the technical debt. Join the conversation on the relationship between Technical Debt and quality in software development. If you are interested in blogging for us, let us know!

Economics of Quality: Technical Liability and Self-insuring Software – A CISQ Presentation

By Frances Lash | December 3, 2014

Screen Shot 2014-10-22 at 10.26.31 PM
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.  In this presentation from CISQ, by Murray Cantor senior consultant at the Cutter Consortium, the ... read more

The Broken Windows Theory of Technical Debt

By Frances Lash | November 6, 2014

Screen Shot 2014-11-06 at 12.56.29 AM
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

Measuring and Managing Technical Debt – A CISQ Presentation

By Frances Lash | October 23, 2014

Screen Shot 2014-10-22 at 10.26.31 PM
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

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

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

Confronting Technical Debt

By Frances Lash | August 28, 2014

There are a lot of posts out there that talk about how to handle technical debt so it doesn’t get out of control and start to affect your system’s performance. This post does address the reality of paying off technical debt, but also goes into detail of how to know where to start refactoring for ... read more

Technical Debt & Quality – Binary Thinking in an Analog World

By Frances Lash | August 27, 2014

Form Follows Function - All Things Architectural.clipular
This is really great post that discusses the idea that ‘quality is not negotiable’ and that ‘only technical debt enthusiasts believe that’. The post states that deciding what is negotiable isn’t really the decision of the developer – because they are not paying for the work, and that by ‘negotiating’ quality they are not tech ... read more

Technical Debt – Why not just do the work better?

By Frances Lash | August 25, 2014

Here is a post that answers the question: why not just do the work better in order to avoid technical debt? Here it is explained that technical debt is not necessarily consciously done poor work (in the mode of code shortcuts) but also a result of many uncontrollable factors – such as the intrusion of ... read more

Feature Toggles are one of the worst kinds of Technical Debt

By Frances Lash | August 20, 2014

mh_dzone_logo
This is great post about how technical debt can accumulate when employing feature flags or toggles into mainline code as a shortcut to release. Feature flags or toggles are used to” build conditional branches into mainline code in order to make logic available only to some users or to skip or hide logic at run-time, ... read more