Technical Debt

images/execution/refactoring/technicalDebt.jpg

Technical debt is the continuous accumulation of shortcuts, hacks, duplication, and other sins we regularly commit against our code base in the name of speed and schedule.

You are always going to have some debt in your code (having none would mean you aren’t trying innovative or different things), but you’ll know you’ve accumulated too much when what used to be fun, easy, and simple is now painful, hard, and complex.

Technical debt can take many forms (spaghetti code, excessive complexity, duplication, and general sloppiness), but what makes it really dangerous is how it just kind of sneaks up on you. Each transgression initially ...

Get The Agile Samurai now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.