Technical debt is a term used to define the cost in terms of resources that are incurred when a programmer goes with a solution to a task that will require some changes or improvements in the future. In layman's terms kicking the can down the road.
Use Cases and Examples
The issue of technical debt is more of a management problem caused by a lack of effective planning and following poor project management practices for the most part.
A typical example is setting up a server that might not scale past a given number of users, this means down the line the developers will have to revisit this setup and make changes.
Technical debt is the price paid for unplanned work that has to be incurred due to poor project management.
Here is another article you might like 😊 "What Is Test Coverage?"