The bottleneck moved from writing code to understanding it. developers average 16.9 hours a week…
the bottleneck moved from writing code to understanding it. developers average 16.9 hours a week debugging, twice their writing time, and 35% of ai-generated code reaches production before the team understands it.
that's from a september survey of 300 senior engineering leaders at $250m-plus companies.
Context
InfoQ reports a survey by the research firm Coleman Parkes, commissioned by Undo, of 300 senior engineering leaders responsible for mission-critical software, most of them working in C and C++. It says respondents spend on average 9.8 hours a week producing code and 16.9 hours a week debugging, which is 42% of the working week, and that 35% of generated code reaches production before the team has fully understood it.
Pivot News describes Undo as a company that sells AI-powered root-cause analysis, and reports the same figures. InfoQ also says 80% of respondents said coding agents struggle with difficult problems in complex codebases.
The 16.9 hours and the 35% match the sources. The sample is leaders of mission-critical, mostly C and C++ teams, so the figures do not describe developers in general. The note says 'developers average', which widens the scope.
The note says debugging is twice writing time. The figures are 16.9 hours against 9.8 hours, which is about 1.7 times. The note's $250m-plus company size and its September timing were not found in the pages read, so those details are unsupported here, not refuted. Both articles are dated October 7, 2026.
The survey was commissioned by a vendor that sells debugging tooling, which is a possible interest in the result. The 35% is a figure for generated code in general, and the sources read here do not say it is specific to AI-generated code that was reviewed or tested.
Related work
- Survey Finds AI-Generated Code Increases Debugging, Failure Rates (InfoQ, October 7, 2026) ↗Source for the survey sample, the 9.8 and 16.9 hour figures, the 42% and the 35%.
- Debugging now eats 42% of the week, Undo-backed survey finds (Pivot News, October 7, 2026) ↗Source for Undo's business and the same figures.
Watch next
- Read the Undo report itself for the sample's company-size and survey-date details. Look for an independent measure of time spent debugging.
Sources
Provenance
The note above is reproduced unedited from the original post, first published on Threads on 9 October 2026 at 02:16 IST. Sources are the papers and datasets the note draws on.
View the original post ↗Embed this note
More notes
The air is now being asked to keep its own ledger
the air is now being asked to keep its own ledger: ecmwf’s aifs compo becomes the first ai model to forecast atmospheric composition globally every three hours, cleanair simulates 365 days of pm2.5 over china in ten seconds, and a unified framework maps six pollutants at one kilometer across the whole country. the air now files its own composition report.
read the note →The current is now being asked to draw its own map
the current is now being asked to draw its own map: china’s langya 2.0 predicts six ocean phenomena including internal waves and mesoscale eddies, a deep net called wenhai resolves eddies globally with air sea flux formulas built in, and scripps infers surface currents from the way temperature patterns deform in satellite images. the ocean now files its own circulation report.
read the note →The soil is now being asked to report its own carbon
the soil is now being asked to report its own carbon: a nix color sensor paired with generative data augmentation predicts soil organic carbon without a lab, random forest drives 74 percent of soil health mapping studies, and sentinel 2 tracks five year carbon change across france and italy from 922 samples. the dirt now files its own carbon account.
read the note →