iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
AI coding tools can make individual developers feel more productive, more able to stay in flow, and more satisfied with their work. The evidence available through 2025 does not show that those gains reliably become faster or safer software delivery. Writing code faster is one step in a longer chain that includes review, testing, release, and operations, and the surrounding organization decides whether a faster step turns into reliable working software.
The phrase “hang on for dear life” captures a pressure that the sources treat as a concern to watch, not as a proven outcome. The studies below measure different things, at different levels, under different conditions. Keeping those distinctions straight is the most useful way to read them.
Writing code faster is not the same as delivering software faster
Delivery performance is usually judged by two things: throughput, meaning how quickly changes move from idea to production, and stability, meaning how reliably those changes perform once they are live. DORA (DevOps Research and Assessment), which publishes the State of DevOps reports, tracks both. A tool that speeds up one stage can leave the other measures unchanged or make them worse, which is why the evidence has to be read level by level.
Free tools Windows power users keep installed
One-click scans. No signup required.
The table below lines up the measures that appear in the sources and the level each one describes.
#1 Best Overall
| What is measured | Level | Reported result and source |
|---|---|---|
| Self-reported productivity, flow, and job satisfaction | Individual developer | Significantly increased with AI adoption, per DORA’s 2024 report |
| Time to complete specific tasks | Individual, in a randomized trial | 19% longer with AI allowed, among 16 experienced open-source developers (METR, 2025) |
| Delivery throughput | Team or organization | A 25% increase in AI adoption was associated with a 1.5% decrease, per DORA’s 2024 model |
| Delivery stability | Team or organization | A 25% increase in AI adoption was associated with a 7.2% decrease, per DORA’s 2024 model |
| Past use of AI coding tools | Survey respondents at large companies | More than 97% had used them at some point (GitHub survey, fielded February 26 to March 18, 2024) |
The most favorable results sit with individual experience and survey-reported adoption. The organizational delivery figures come with warnings, and the one controlled timing test ran against the simple speed-up story.
What DORA’s 2024 report found
DORA’s Accelerate State of DevOps Report 2024 offers the clearest split between individual and delivery outcomes. Its AI findings report that AI adoption significantly increased individual productivity, flow, and job satisfaction, while negatively affecting delivery stability and throughput.
Individual gains
The individual gains are measured through how developers report their own work: whether they feel productive, whether they stay in flow, and whether they are satisfied. Those are real outcomes for the people using the tools. On their own, they do not show that the organization ships better software sooner.
Throughput and stability
The delivery figures come from the model described in DORA’s Impact of Generative AI in Software Development summary. A 25% increase in AI adoption was associated with a 1.5% decrease in delivery throughput and a 7.2% decrease in delivery stability. These are associations inside that report’s model. They are not causal guarantees and should not be applied as a universal rule to any particular team.
The same summary recommends preserving small batch sizes and robust testing. It presents both as fundamentals that continue to matter when AI is part of the workflow.
Trust in AI output
The summary also reports that 39% of developers trust AI outputs “a little” or “not at all.” That figure does not measure delivery directly, but it is a reasonable explanation for why verification stays in the workflow. Code a developer does not fully trust still has to be reviewed and tested, so faster generation does not remove those steps.
What DORA’s 2025 report adds: AI as an amplifier
The 2025 report, State of AI-assisted Software Development, draws on more than 100 hours of qualitative data and survey responses from nearly 5,000 technology professionals around the world, as described in DORA’s 2025 report listing on Google Research. Its central conclusion is that AI primarily amplifies existing organizational strengths and weaknesses.
The report puts the point this way: “The greatest returns on AI investment come not from the tools themselves, but from a strategic focus on the underlying organizational system.” That is a finding of the report, not a quotation from an individual speaker.
Rank #3
The amplifier framing is the most useful way to read the earlier figures. A team with stable priorities, solid tests, and clear communication has more to gain when AI speeds up its work. A team already struggling with unclear direction or fragile releases is more likely to see those weaknesses surface sooner.
The 2024 and 2025 reports should be read side by side with care. They use different data, different models, and different framings. The 2024 summary reports negative associations with delivery measures, while the 2025 report describes the outcome as a function of the surrounding system. The two point the same way on context, but their figures should not be merged into a single number.
The controlled trial that found experienced developers slower
The clearest challenge to simple speed-up claims is a randomized controlled trial by Becker, Rush, Barnes, and Rein of METR, reported in an arXiv abstract titled “Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity”, dated July 12, 2025.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →How the trial was run
- Sixteen developers with moderate prior AI experience completed 246 tasks.
- They worked on mature open-source projects where they had an average of five years of prior experience.
- The tools were early-2025 tools. The abstract says participants primarily used Cursor Pro with Claude 3.5 and 3.7 Sonnet.
- Measured task completion took 19% longer on tasks where AI was allowed.
Expectation versus measurement
Participants expected AI to speed them up, and afterward they believed it had. The timed measurement pointed the other way. That gap matters for teams that rely on how a tool feels. A developer’s sense of progress is useful information about the experience, but it is not the same as a measured change in how long work takes.
What the trial does not establish
The authors note that experimental artifacts cannot be entirely ruled out. The sample was small, the tasks were specific, and the tools have changed since early 2025. The result should not be generalized to novice developers, greenfield projects, all current models, or team-level delivery. It is evidence against the claim that AI always speeds up experienced developers on familiar codebases. It is not evidence of a general slowdown across the industry.
Adoption is high, but the GitHub survey measures use, not impact
GitHub’s survey, published on the GitHub blog (dated August 20, 2024 and updated April 15, 2025), found that more than 97% of 2,000 respondents across the U.S., Brazil, India, and Germany had used AI coding tools at some point. Wakefield Research fielded the online survey for GitHub from February 26 through March 18, 2024.
Several limits matter when reading it:
- The sample was 2,000 non-student enterprise respondents, 500 per country, working at companies with more than 1,000 employees. Respondents were not managers.
- The question asked whether people had used AI coding tools at any point. It did not ask how often they use them, so the 97% figure is not evidence that 97% use AI daily.
- The survey measures adoption and self-reported experience. It does not show that AI caused any improvement.
- GitHub sells developer tools, so its benefit claims come from a company with a commercial interest in them.
The article also quotes Kyle Daigle, GitHub’s Chief Operating Officer: “AI doesn’t replace human jobs—it frees up time for human creativity.” That is a company leader’s view, not an independently verified finding about job impact.
The human side: concerns the evidence raises but does not settle
The headline is about people as much as speed. The sources document concerns that teams need to address, but they do not prove the outcomes many readers fear.
Best Value
Job security
Concerns about job displacement appear across the material. DORA’s 2024 summary explicitly recommends a clear AI strategy and open communication about job-security concerns, and it associates alleviating those concerns with higher team AI adoption, as covered in the conditions section below. Nothing in these sources establishes whether AI reduces the number of developer jobs.
Does AI make developers work harder?
The sources do not establish that AI causes overwork. The risk that saved time gets absorbed by new organizational demands is a plausible hypothesis, and it fits the amplifier framing. If faster output raises expectations for more features, more reviews, or more releases, time saved in coding can disappear into other work. That mechanism remains a hypothesis, not a measured result.
Burnout is also easy to misattribute. DORA’s 2024 summary links unstable priorities to lower productivity and higher burnout. That is a finding about organizational conditions, not about AI. A team whose priorities keep shifting may feel exhausted whether or not it uses AI, so the source of the strain should be identified before the tool is blamed.
Recommended Free Tools
Developer experience
The 2024 report puts the human point plainly: “Software doesn’t build itself. Even when assisted by AI, people build software, and their experiences at work are a foundational component of successful organizations.” Treating developer experience as a delivery input rather than a side effect is consistent with the organizational focus of the 2025 report.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Organizational conditions associated with better outcomes
DORA’s 2024 summary reports associations between team AI adoption and several organizational practices. The figures below are relative associations from the report’s model. They are not guaranteed effects of making a change, and they should not be read as a forecast for any one team.
| Condition | What the 2024 summary reports |
|---|---|
| Alleviating job-security concerns | Associated with 125% more team AI adoption |
| Dedicated work-hour learning time | Associated with a 131% increase in team AI adoption |
| Clear acceptable-use policies | Associated with a 451% increase in team AI adoption |
| Stable priorities | Unstable priorities are linked to lower productivity and higher burnout; not stated as an adoption figure |
| User-centric work | Aligned with better developer experience; not stated as a figure |
| Supportive transformational leadership | Aligned with better developer experience; not stated as a figure |
A diagnostic checklist for your own team
These questions help you test whether AI is improving delivery or only changing how work feels. None requires a controlled experiment, and each one shows which level a claim belongs to.
Quick Recap
- Which level is the claim about: an individual’s experience, a timed task, or team-level delivery?
- Are throughput and stability being tracked together? Both declined in the 2024 model’s associations, so a gain in one that hides a loss in the other is not a delivery improvement.
- Has batch size changed? Larger changes arriving faster are harder to review and test.
- Are automated tests and review capacity keeping pace with generated code?
- Have priorities stayed stable across the period being measured?
- Is there a written acceptable-use policy, and do developers know it?
- Has leadership said, in specific terms, how AI affects roles and how saved time will be used?
- Are saved hours being reassigned to new work without anyone naming that decision?
Questions the sources do not answer
- Causation in the adoption figures. Teams that were already well run may be more likely to adopt AI and to adopt the practices above, so the associations cannot tell whether those practices cause higher adoption.
- Persistence over time. The 2025 amplifier finding describes a point in time. None of the sources tracks whether its patterns hold over several years.
- Workload after time is saved. No source measures what happens to developers’ hours when AI-saved time is reassigned, so the absorption question remains open.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute
