Tag: software maintenance

Strategies to fix technical debt is a topic that’s not going unnoticed this year.
Technical Debt for Continuous Innovation: Strategies to Avoid
A distinction that we always try to make in our posts is that there is both good and bad technical debt. This is similar to how there are ways in which financial debt can be used to strategically help a company
Technical Debt The Right Way
Last week we published a post about the Consortium for IT Software Quality's (CISQ) initiative to come up with a standard technical debt measure through a survey distributed to developers.
Contribute to CISQ's Technical Debt Remediation Survey
Cars are no longer simple pieces of machinery, but have evolved into highly integrated pieces of technology - with software embedded into all their critical systems.
Technical Debt & Safety Critical Systems in Automobiles: The Road Ahead
There are always trade offs to be made when you're dealing with keeping your application portfolio up-to-date. You always have several options, whether it be modernization through migration/refactoring or by a sort of "transformative leap".
How to Mitigate the Technology Gap and Manage Technical Debt
Technical debt starts off from building fast and making a slew of decisions based on short-term needs that are detrimental to your products long-term stability and maintainability.
Technical Debt: What is it and What to do When You Have it?
Here, at On Technical Debt, we often discuss the difficulties of communicating technical debt to business stakeholders, the consequences that arise from it, and the ways to about paying it back - but in this post we are going  to focus on why it is there to begin with.
The "Why" of Technical Debt
Remodeling software should be done in the same mindset under which we remodel a house: to make it last longer and run better. Companies should be invested in mending their code to be able to get more productivity out of it.
Stop Paying Back Technical Debt, Accumulate Technical Wealth
In the evolution of technology, one of the major components of its trajectory is that it has become integrated in every possible product.
Software and Code Quality in Automobile Safety-Critical Applications
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
A CFO's job is to form a company's investment strategy, and one critical area of investment in any organization is technology.
A CFO's Guide to Technical Debt
A relationship that is often overlooked in software development and maintenance is the one between incidents and technical debt.
The Relationship Between Incident Management and Technical Debt
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
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
Often times in the development process large amounts of technical debt result in stalled innovation from a given team.
How Innovation Debt Is Just As Damaging as Technical Debt
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 technical debt.
Maintaining Technical Debt and Team Morale in a Large System