Skip to main content

Technical Debt

Learn Technical Debt (Engineering Practices, Software Fundamentals) with worked examples, diagrams and interview questions. Free on JavaSchoolLab.

What is Technical Debt? Technical debt is the extra work created in the future because a team chose a quick/easy solution now instead of a better, more thorough one. The term comes from finance - like a loan, it gives you speed today but "interest" (slower development, more bugs) accumulates until it's paid off (refactored). Real-world analogy: taping over a leaking pipe to stop a flood right now, instead of properly re-plumbing it. It works today, but if you never come back to fix it properly, it eventually leaks again - possibly worse.

More lessons in Engineering Practices