42% of Developers Say AI Writes Half Their Code

42% of Developers Say AI Writes Half Their Code

Estimated reading time: 5 minutes · Last updated:

BairesDev’s Q3 2026 Dev Barometer finds that 42% of respondents say AI now writes at least half of their code, up from 12% in Q3 2025. The survey polled 705 developers across more than 60 countries and collected answers from 41 enterprise CTOs. BairesDev’s figures show AI reduces the time spent producing code by roughly 13 hours per week on average, but those hours are being redirected into activities such as code review, debugging and learning new tools rather than lowering overall workload; BairesDev CEO Darren Shimkus called the shift “a layer above the code,” saying human validation has become the bottleneck, as first reported by VentureBeat.

Developers nearly doubled the time AI saves them in coding, to 13 hours a week. Not one of those hours came back.

Darren Shimkus, BairesDev CEO

Key takeaways

  • Adoption jump: BairesDev found 42% of developers say AI writes at least half their code in Q3 2026, up from 12% in Q3 2025.
  • Time use: Developers report AI now saves about 13 hours of coding per week, versus roughly seven hours a year earlier.
  • Workshift: Only 21% of developers spend more than half their workweek writing new code from scratch; 67% spend more time reviewing AI output.
  • Enterprise response: Among 41 CTOs surveyed, 78% increased spending on code review, quality assurance and validation to support AI-generated work.

Survey snapshot: sample, scope and the headline increase

BairesDev’s Q3 2026 Dev Barometer polled 705 developers across more than 60 countries and 41 enterprise CTOs. The developer sample is composed largely of applicants participating in BairesDev’s screening process rather than only the company’s employees, and the CTO sample is substantially smaller than the developer sample. The headline metric is a rise from 12% in Q3 2025 to 42% in Q3 2026 in the share of developers who say AI writes at least half their code. That is a change of 30 percentage points between the two quarters.

The report sits alongside several large-scale surveys that show the same pattern: JetBrains’ 2026 Developer Ecosystem Survey sampled more than 15,000 professional developers and found 90% use AI coding agents at least weekly, with 68% using them daily; Stack Overflow’s 2025 Developer Survey drew more than 49,000 responses and reported 80% using AI tools but only 29% trusting their accuracy. Those external datasets give context to BairesDev’s sample, which mixes applicants and practitioners.

Where developer time actually went: coding saved, review and learning rose

BairesDev reports that AI now saves developers 13 hours of coding per week, nearly double the roughly seven hours reported a year earlier. The extra time has not translated into idle capacity: only 21% of respondents say they now spend more than half their workweek writing new code from scratch, while 67% report spending more time reviewing AI-generated code and 52% report spending more time debugging problems introduced by AI.

The survey also finds a jump in formal upskilling: developers report averaging nine hours per week learning AI tools and other new technologies, up from four hours a year ago. That five-hour increase in weekly learning is comparable in scale to the additional review and debugging work respondents describe, and BairesDev’s CEO Darren Shimkus summarised the shift by saying, “Developers nearly doubled the time AI saves them in coding, to 13 hours a week. Not one of those hours came back.”

Enterprise reaction: more validation, not full delegation

The CTO responses indicate organisations are funding human checkpoints rather than delegating production decisions to agents. Among the 41 CTOs surveyed, 78% said they had increased spending on code review, quality assurance and validation to support AI-generated work. At the same time, only 7% of developers said the decision to ship code had been entirely delegated to AI without their input.

Shimkus told VentureBeat that enterprise customers are treating developer explainability as non‑negotiable for production systems: if an engineer cannot explain what AI-generated code does and why, the organisation will not permit that engineer to check it in. That distinction—greater autonomy for prototypes, strict human review for production—helps explain why spending has shifted into review processes even as AI generates larger code volumes.

How this reshapes skills, pay and security priorities

The barometer shows AI fluency is already affecting compensation and promotion. Among developers who received raises in 2026, 29% identified AI tool fluency as the driver, followed by system design and architecture at 20% and human skills such as communication and mentorship at 15%. Yet only one in four CTOs said they were actively investing in human‑skills development, a mismatch BairesDev flags as a strategic gap.

Security and governance are rising on the agenda as agentic systems take on actions beyond code generation. BairesDev points to external research reported by ITPro that finds limited use of deployment gates and governance around agents. The company’s advice—go deep in security and in one AI tool rather than many—echoes Shimkus’s warning that organisations can buy tools but not necessarily the judgment to apply them safely at scale.

How recent developer surveys compare on AI adoption and trust
Survey Sample AI-use / headline Trust or impact metric
BairesDev Q3 2026 705 developers; 41 CTOs 42% say AI writes at least half their code Developers report 13 hours saved; 67% more time reviewing
BairesDev Q3 2025 Earlier Dev Barometer 12% said AI wrote at least half their code Developers reported about 7.3 hours saved
JetBrains 2026 15,000+ developers 90% use AI coding agents at least weekly; 68% daily Adoption of agents is widespread
Stack Overflow 2025 49,000+ responses 80% using AI tools Only 29% trusted accuracy; 66% fixing AI code

How the trend could evolve

The case for

  • Wider adoption of AI coding agents could raise overall team productivity if enterprises standardise validation pipelines and reuse safe patterns.
  • Investing in security and review tools alongside developer training could shorten the validation bottleneck and restore usable developer capacity.

The case against

  • If organisations underinvest in human skills and governance, time saved on drafting could be absorbed entirely by debugging and compliance work, leaving net capacity unchanged.
  • Agentic systems rushing into production without deployment gates could increase operational risk and incident costs for complex software systems.

What to be careful about

  • Overreliance on an applicant-heavy sample: BairesDev’s developer respondents are largely applicants, which may bias measured adoption rates versus a purely employed practitioner sample.
  • Rising security exposure from agentic systems if enterprises do not adopt stronger deployment gates and governance mechanisms.
  • Mismatch between skills rewarded (AI fluency) and employer investment in human skills, risking stagnation in leadership and cross‑functional competencies.

The bottom line

BairesDev’s Q3 2026 Dev Barometer shows a rapid increase in AI-generated code volume, but the practical effect is a reallocation of developer effort rather than freed capacity. Engineers report an extra 13 hours of AI-saved coding time per week, yet those hours are absorbed by review, debugging and learning; organisations are responding by increasing spending on validation. For employers the implication is clear: tools alone do not replace judgment—investment in review pipelines, security controls and human skills will determine whether AI raises team productivity or simply shifts costs.

What to watch

  • Watch for BairesDev’s next Dev Barometer release; no date has been set.
  • Watch for enterprise guidance or public policies on deployment gates for agentic development; no date has been set.
  • Watch for major vendors or large enterprises publishing standards for AI-generated code validation; no date has been set.

Frequently asked questions

How many developers said AI writes at least half their code?

BairesDev’s Q3 2026 Dev Barometer found 42% of the 705 developers surveyed say AI writes at least half their code, up from 12% in Q3 2025.

Are developers spending less time coding overall?

No: only 21% of respondents now spend more than half their workweek writing new code from scratch, and 67% report spending more time reviewing AI-generated code.

Is trust in AI-generated code improving?

Trust appears limited: Stack Overflow’s 2025 survey found only 29% trusted AI accuracy, and 66% reported spending more time fixing AI-generated code that was "almost right."



Share:

Categories

Newest course every month

Advertise your offline course to a wider audience with our landing page.

You May Also Like

BairesDev's Q3 2026 Dev Barometer finds 42% of developers say AI writes at least half their code, while review, debugging...
Visual Studio Code is Microsoft’s free, cross-platform code editor; this guide summarises its features, download steps, extension ecosystem and pros...
Visual Studio Code is Microsoft's free, cross-platform code editor with Git, debugging, extensions, AI and remote tools. This guide explains...