# The Real Cost of Technical Debt

DevFeed: [The Real Cost of Technical Debt](<https://devfeed.tech/articles/the-real-cost-of-technical-debt-21066.md>)

Original publisher: [Read original article](<https://jakeyesbeck.com/2016/03/06/the-real-cost-of-technical-debt/>)

Published: 2016-03-06T12:00:00Z

Content type: opinion

Language: en

Sources: [Jake Yesbeck](<https://devfeed.tech/sources/jake-yesbeck.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [Software](<https://devfeed.tech/topics/software.md>), [App](<https://devfeed.tech/topics/app.md>), [web applications](<https://devfeed.tech/topics/web-applications.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [communication](<https://devfeed.tech/tags/communication.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [financial](<https://devfeed.tech/tags/financial.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [scope](<https://devfeed.tech/tags/scope.md>), [shortcuts](<https://devfeed.tech/tags/shortcuts.md>), [software-engineer](<https://devfeed.tech/tags/software-engineer.md>), [technical](<https://devfeed.tech/tags/technical.md>), [web](<https://devfeed.tech/tags/web.md>)

## AI overview

The article explains technical debt as the future work created when software teams use shortcuts to meet immediate time or external pressures. It argues that unchecked debt increases complexity, expands the scope of seemingly simple changes, and can seriously damage a software application. The article recommends communicating the long-term cost of fast solutions and planning regular efforts to reduce accumulated overhead.

## Source excerpt

Writing software is an iterative process. Rarely is software written and then never revisited. When this iteration occurs, a software engineer is presented with multiple options. Usually, a single objectively correct option is present but may not be chosen due to time constraints or other outside pressures. When shortcuts are taken to alleviate these external pressures, technical debt is often accrued. Permit Today, Pay Tomorrow Technical debt is referred to as such due to its similarities with financial debt. A credit card enables a person to complete a purchase they may not otherwise be able to, resulting in a bill to be paid by that person in the future: a debt. Technical debt is the same concept; a current feature or product is completed faster than previously possible at the cost of future work: a technical debt. If not apparent from name alone, technical debt is not a desired feature in a healthy software system. This debt can often appear benign, giving no cause for alarm or prompt resolution; however, I believe that thinking to be in error. Technical debt can severely damage a software application and may even cause its destruction. Solution: Communicate the Importance of the Correct Approach Open communication about why a solution might be slower to accomplish now, but result in a healthier system for the future can be very important. A conversation about the amount of technical debt a "fast" solution will generate might help reduce pressure. Ongoing Overhead Left unchecked, technical debt can become a constant complexity or time increasing abscess for an otherwise healthy software application. Suddenly, every task that must interact with or touch technical debt affected code is not as simple as it should be. The "simple change" that a product team might request can have its scope increased due to technical debt overages. For example, we can assume that a typical web application decides that its new mobile friendly version should be a parallel implementatio