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!

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 off paying of 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

Software Process and Measurement Cast 301: Technical Debt Essay

By Frances Lash | August 19, 2014

spamcast-300dpi
Here’s a podcast of an essay on technical debt that delves into the reality of using technical debt and the payment of that debt. Thomas Cagely, the host, goes on to describe the practice of documentation, auditing, standards and processes maintenance, and technical debt ‘sizing and valuing’. He mentions possible strategies to maintain software, and ... read more

Technical Debt – Breaking the Poor Development Cycle

By Alexandra Szynkarski | April 30, 2014

Technical Debt Cycle
A comprehensive treatment of the cost and impact of technical debt on the developer, the team and the mission. This post illustrates the vicious cycle that technical debt causes for the development organizations, including frequent incidents and hot-fixes, resulting in deprecating condition of the code base. It also talks about some techniques to break out ... read more

Technical Debt in the Era of Transient Competitive Advantage

By Israel Gat | September 4, 2013

SpaghettiCode_II
A situation that I and various consultants in the Cutter Agile Practice are often exposed to is a pressing need to reduce technical debt. A prospect calls with respect to some software assets that have ceased to perform adequately. What we almost invariably find once we do the Technical Debt Assessment is that over time the client’s codebase got ... read more

Are We There Yet? Thoughts on Technical Debt Research and Practice

By Zadia Codabux | July 26, 2013

Directions
The strategic management of technical debt has gained visibility with the increase in popularity of agile methods. Consequently, it is of extreme importance to focus research on understanding, quantifying and properly managing technical debt. In the software engineering research community, there is a lack of consensus among stakeholders regarding what technical debt really is. There ... read more

Can Technical Debt Be Quantified? The Limits And Promise Of The Metaphor

By Matt Holford | March 19, 2013

Quantifying Technical Debt
Anyone whose professional life has intersected with the technical debt metaphor knows its power: the simple proposition that such a thing exists opens up a new channel of communication among groups (IT and application developers, designers, biz dev) that famously have trouble communicating about technical decisions. Not everyone understands test cases, aging platforms, crufty code bases, or security loopholes, ... read more

CISQ Webinar: The Future of Software Sizing with Automated Function Points

By Alexandra Szynkarski | February 5, 2013

IT-CISQ-Function Points
Consortium for IT Software Quality (CISQ) have recently announced the availability of an OMG Specification for Automated Function Points (AFP). Functions points (or source lines of code) have been used as a basis for quantifying and understanding the size of Technical Debt in several recent studies. This new OMG specification is the first, new, consistent, automatable code ... read more