Tag: Software Quality

In simple terms, technical debt is the work that you've been putting off that is needed in order to complete a job.
Get a Grip on your Technical Debt
Mergers and acquisitions can always result in some sort of unplanned issue emerging – whether it be about competition or integrating two disparate IT or HR systems.
On Technical Debt and Mergers and Acquisitions
One of the greatest issues of dealing with technical debt is the brittle code that comes along with it.
How to Avoid the Brittle Code of Technical Debt
Most technical professionals can agree on at least one thing: that things would've been done better and problems would've been solved quicker if they had more time to work on them and if they knew the how negatively the impact of not dealing with these issues would effect software quality.
How To Deal with Technical Debt in Different Environments
Ward Cunningham, when coining the term technical debt, warned of incremental debt that allows code to run effectively but imperfectly.
The Path from Technical Debt to Bad Code
This post presents an interesting mindset from which to build software: treating infrastructure as code so that the systems and devices which are used in software are treated as software themselves.
Infrastructure as Code and Avoiding Technical Debt

We always hear about issues with systems, applications, or services caused by poor code quality or missed defects, but what happens when these problems become life threatening? Recently an article posted by npr discussed the early release of dangerous prisoners who are now being charged for murder. According to the article, Governor Jay Inslee of Washington State reported that more than 3,200 prisoners were released early due to a software defect.

A Code Quality Problem in Washington State Puts Dangerous Criminals Back on the Street
Arlene Minkiewicz, Chief Scientist at Price Systems, recently  presented on the issues relating to technical debt and software maintenance.
At the Intersection of Technical Debt and Software Maintenance Costs
It is common practice for a developer to make a quick fix in a software project and to then move onto the next shiny new feature.
Technical Debt and Reverse Grind: How to Manage it
There has become a recent trend in discussing the benefits of machine learning - however, despite its recent popularity there are few large-scale systems that actually employ it in production.
The Machine Learning Hype Dampened by Technical Debt
In 2015 there was a major slew of headlines dedicated to software failures at major companie which led to a discussion of best practices for software development.
Improving Software Quality to Avoid System Failure
In this great podcast from .Net Rocks! the discussion on how to handle technical debt takes an interesting turn towards the discrepancy in communication between different stakeholders on a software project.
Technical Debt and Breaking Down "Tribal Speak"
Much of what comes with being an entrepreneurial leader is knowing when to accept certain tradeoffs.
When You Should Start Paying Off Your Technical Debt
It has become a recent practice in organizations to measure technical debt in their software.
The Risks of Measuring Technical Debt
Technical debt is a very important concept to developers that is often lost on the management end. Developers use the concept to describe the consequences of a pressure to meet deadlines.
Technical Debt and Risk: One and the Same
It's estimated that the federal government spends about $80 billion a year on IT.
Technical Debt & Software Quality Tools

Application portfolio analysis was at the center of discussion as Forrester Research Vice President and Principal Analyst, Margo Visitacion, presented how Agile development is affecting the application development process and IT’s portfolio planning. Ms. Visitacion explained that in the “Age of the customer,” they want more for less and expect companies to fluidly change based on their needs and demands. As companies shift their attention to customers’ experiences rather than production figures, it’s leading directly to higher revenue and a longer-lasting relationships.

Key Discussion Points from Forrester Webinar: Agile Portfolio Management Requires Rapid Transparency

Software risks to the business, specifically Application Resiliency, headline a recent executive roundtable hosted by CAST and sponsored by IBM Italy, ZeroUno and the Boston Consulting Group.  European IT executives from the financial services industry assembled to debate the importance of mitigating software risks to their business.

Software Risk: Executive Insights on Application Resiliency

In the current tech scene, it has become common practice to refer to programmers as engineers. It seems that if you aren't part of sales or marketing teams you are now entitled to being designated as an engineer. However, what has been forgotten over the 50 years of looking to turn software development into a legitimate engineering practice, is that we still haven't reached the aspiration of being just that: a legitimate engineering practice. Traditional engineers have to go through stringent regulation, certification, and apprenticeships in order to gain the title. This creates an implicit responsibility of providing reliability and public safety. Software development hasn't reached this point yet - software quality and standards are not universally valued.

So why is the tech industry using the engineering title to describe its technical workers?

Faltering Software Quality and Standards: Why Programmers Should Stop Calling Themselves Engineers