Technical debt
In software development and other information technology fields, technical debt (also known as design debt or code debt) refers to the implied cost of additional work in the future resulting from choosing an expedient solution over a more robust one. While technical debt can accelerate development in the short term, it may increase future costs and complexity if left unresolved.
Technical debt - Wikipedia Jump to content From Wikipedia, the free encyclopedia Cost of maintaining a low quality system Technical debt (also known as design debt [ 1 ] or code debt ) is a qualitative description of the cost to maintain a system that is attributable to choosing an expedient solution for its development. [ 2 ] While an expedited solution can accelerate development in the short term, the resulting low quality may increase future costs if left unresolved. [ 3 ] The term is often used in the context of information technology and especially software develop
saved by
related reading
- Technical Debt | Glossary | ProductPlanproductplan.com
- What Is Technical Debt: Common Causes & How to Reduce It | DigitalOceandigitalocean.com
- Managing technical debt at an agile companyvadimkravcenko.com
- 3 Kinds of Tech Debt | Byte Size Theoriesbytesizetheories.com
- Stop saying “technical debt” - Stack Overflowstackoverflow.blog
- Cognitive load is what mattersminds.md
- How To Do Lessalexturek.com
- Most Technical Problems Are Really People Problemsblog.joeschrag.com
- Tech debt metaphor maximalism - apenwarrapenwarr.ca
- Design smell - Wikipediaen.wikipedia.org
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- Understanding Technical Design Document and Writing Guidekimi.ai