Technical debt
Technical debt is the extra future cost created when a team chooses a faster or simpler way to build something now instead of the more thorough approach, so that later changes to the same part of the system take longer or carry more risk than they otherwise would.
Submit a project Rank your technical debt by costReviewed by David Nguyen (CEO) · Updated 6 Oct 2026 · 3 min read
This term is one of the entries in the OutsourcingVN glossary of words buyers meet while weighing maintenance against new features.
Why it matters
Every shortcut speeds up the moment it is taken and slows down every moment after, in the part of the system it touches — the same relationship a loan has to interest. Left untracked, technical debt accumulates quietly until a routine feature request takes weeks instead of days, and nobody can say why. OutsourcingVN is operated by Netbase JSC, and naming debt explicitly is what turns "the code feels slow to change" into a prioritised, fundable list.
An example in practice
A team ships a feature by copying a chunk of logic into three places instead of writing one shared function, because a release date was close. Eighteen months later, a rule in that logic needs to change, and it has to be found and changed in three places, with one of them missed in the first release. The missed copy is the interest that particular debt has been charging ever since it was taken on.
Common misreadings
Technical debt is not simply "bad code" — a deliberate, documented shortcut taken to meet a real deadline is still debt, and sometimes the right call; the problem is carrying it unrecorded and unpaid indefinitely. It is also not a score a static-analysis tool can output on its own: the business cost of a given shortcut depends on how often that part of the system changes, which a tool cannot see. And paying down debt is not the same project as adding a feature, even when the same code is touched — conflating the two is how remediation work quietly stops getting funded.
Plan the next step for your project
Common questions
Ward Cunningham, in 1992, using the debt-and-interest metaphor to explain why a shortcut has an ongoing cost.
No — a shortcut taken deliberately to meet a real deadline can be the right call, provided it is recorded and paid down later.
Related decisions
Turning a list of known shortcuts into a ranked, fundable remediation plan is the subject of the technical debt assessment guide. When ageing code is standing between you and a feature you need, describe the system and the change you are trying to make, and Netbase will respond through Netbase's own outsourcing-services platform; submit a project when you are ready.