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!

Managing Code Quality and Technical Debt

By Frances Lash • April 26, 2016

Technical debt is often given a bad name in the development process. This stems from the fact that when it becomes a topic of … read more

 

On Technical Debt and Mergers and Acquisitions

By Frances Lash • April 21, 2016

Mergers and acquisitions can always result in some sort of unplanned issue emerging – whether it be about competition or integrating two disparate IT … read more

 

Infrastructure as Code and Avoiding Technical Debt

By Frances Lash • March 18, 2016

This post presents an interesting mindset from which to build software: treating infrastructure as code so that the systems and devices which are used … read more

 

Improving Software Quality to Avoid System Failure

By Frances Lash • February 25, 2016

In 2015 there was a major slew of headlines dedicated to software failures at major companies (US Airlines, Wall Street Journal, the New York … read more

 

Maintaining Technical Debt and Team Morale in a Large System

By Frances Lash • January 28, 2016

In this post from InfoQ, Thomas Bradford explains his experience on working with a monolith java-based system that had improper test coverage and huge … read more

 

When You Should Start Paying Off Your Technical Debt

By Frances Lash • January 25, 2016

Much of what comes with being an entrepreneurial leader is knowing when to accept certain tradeoffs. When you have a whole organization under your … read more