The hours ai frees are now spent answering for the code. the q3 dev barometer, fielded across 705…
the hours ai frees are now spent answering for the code. the q3 dev barometer, fielded across 705 developers, finds nearly 80 percent spend less than half their week writing code, saving about 13 hours that mostly go to review.
the bottleneck just moved downstream.
Context
BairesDev's press release of September 15, 2026 reports its Q3 2026 Dev Barometer, a vendor-run quarterly survey of 705 developers across 60+ countries and, for the first time, 41 enterprise CTOs. It says developers now save 13 hours a week coding with AI, nearly double the seven hours reported a year ago, and that only 21% spend more than half their week writing new code from scratch. It says 67% spend more time reviewing AI-generated code and 52% more time debugging AI-introduced problems than a year ago, and that the saved time is being reinvested a layer above the code in reviewing, debugging and upskilling, including 9 hours a week learning.
All figures are vendor-reported and self-reported answers compared with a year earlier, and are not measured time use or causal. The 21% means about 79% spend half the week or less writing new code from scratch, which excludes other kinds of coding work. The release splits the saved hours across reviewing, debugging and learning and gives no hours-per-activity breakdown in the passages read, so mostly go to review is the author's summary. The method and field dates in the executive summary PDF were not read. The bottleneck just moved downstream is the author's line.
Related work
- The hours ai freed went straight into answering for the code ↗An earlier note on the same Q3 2026 barometer.
- The 13 hours a week ai saves developers are going to review ↗Another earlier note on the barometer's 13 hours figure.
Watch next
- The executive summary PDF for method and field dates.
Sources
Provenance
The note above is reproduced unedited from the original post, first published on Threads on 22 September 2026 at 06:05 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 →