The term “technical debt” was coined over a decade ago to help highlight a common problem in software development. Generally you can think of technical debt like this:
The cost of additional rework created by choosing an easy, shortcut solution now instead of the better approach that would take longer.
Delivering software to meet deadlines or functional goals that are wrought with technical debt is like buying items before you can afford them. Both practices can drastically affect your ability to reach your future goals, both long term and short term.
This article is a gentle reminder to recognize, fix, and avoid technical debt in your software projects.