Developers are spending a third of their workweek fighting code that already exists

Stripe's Developer Coefficient survey — still one of the most-cited data points on this despite being a few years old, and reaffirmed by newer 2026 research — found developers spend about 13.5 hours of a 41-hour workweek specifically on technical debt: maintaining, debugging, and refactoring existing code rather than building anything new. Add in time lost to generally bad code and the figure rises to over 17 hours, roughly 42% of the working week.

That number connects directly to a retention problem, not just a productivity one. Stack Overflow's developer survey found technical debt is the single biggest source of workplace frustration developers report — ahead of pay, ahead of management — cited by 62-63% of respondents depending on the survey year. Multiple 2026 studies put developer burnout prevalence at 80% or higher, with close to half of burned-out developers saying they've considered leaving the industry entirely, not just their current job.

The pattern engineering leaders keep missing, according to several of this year's burnout studies, is treating it as an individual resilience problem rather than a structural one. The drivers that show up most consistently — high workload, inefficient processes, unclear goals — are management and process problems, not personality problems, which means the fix has to be structural too.

The concrete step that shows up repeatedly in this year's guidance: budget technical debt work like any other line item, not as something teams get to “if there's time” — a fixed 10-20% of every sprint dedicated to cleanup and refactoring, made visible on the same board as feature work, rather than an invisible tax nobody planned for.