Technical Debt
Domain: Refactoring
π― Motivation
Technical debt is the hidden cost of quick-and-dirty solutions. Like financial debt, it accumulates βinterestβ β each future change takes longer because of earlier shortcuts.
π Concrete Example
Skipping tests to ship a feature fast is debt. Later, every change risks breaking something, and the time you βsavedβ is paid back with interest through slower, scarier updates.
π Analogy
Using a credit card to buy now feels free, but interest compounds. The longer you wait to pay, the more expensive it gets β code shortcuts work the same way.