What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
AI coding assistants are already part of many developers’ daily work, and some controlled and field studies have measured real speed or output gains on specific tasks. The evidence does not show that every developer becomes faster, and it does not establish that AI has already caused broad job losses among software developers. Four things are often blurred together: measured task performance, self-reported experience, organizational effects, and employment trends. Each one answers a different question.
Does AI actually make developers faster?
It depends on the task, the setting, and how output is counted. The two most rigorous productivity studies measured different things, so they cannot be compared directly.
As an Amazon Associate I earn from qualifying purchases.
A controlled task: the 2023 Copilot experiment
In a Microsoft Research experiment published in February 2023, recruited developers were asked to implement a JavaScript HTTP server as quickly as possible. The group with access to GitHub Copilot finished 55.8% faster than the control group. That is a precise result for one defined task with one group of participants. It is not an estimate of how much faster developers are at software work in general. A developer who spends most of a week on system design, debugging an unfamiliar codebase, or coordinating with other teams is doing work this experiment did not measure.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Ordinary work at three companies
A later study, “The Effects of Generative AI on High-Skilled Work: Evidence from Three Field Experiments with Software Developers” by Cui, Demirer, Jaffe, Musolff, Peng, and Salz, moved into normal employment. The three field experiments randomized access to an AI coding assistant among developers at Microsoft, Accenture, and an anonymous Fortune 100 company, covering 4,867 developers. The authors estimate a 26.08% increase in completed tasks, with a standard error of 10.3%.
Two qualifications matter. First, the individual experiments were noisy and their results varied, so the combined figure is an average across these settings, not a forecast for any one team. Second, the gains were not uniform: less experienced developers adopted the tools at higher rates and gained more from them. Microsoft Research posted the paper in June 2025, and it was published online in Management Science on February 27, 2026.
The measured results side by side
| Study | Setting | What was counted | Reported result | Main limit |
|---|---|---|---|---|
| Copilot HTTP server experiment (Microsoft Research, February 2023) | Recruited developers implementing one JavaScript HTTP server | Time to finish the defined task | Treatment group finished 55.8% faster than control | One task and one controlled group; does not represent all software work |
| Three field experiments (Cui et al., Microsoft Research June 2025; Management Science online February 27, 2026) | Ordinary work at Microsoft, Accenture, and an anonymous Fortune 100 company; 4,867 developers | Completed tasks under randomized access to an AI coding assistant | 26.08% increase in completed tasks (standard error 10.3%) | Individual experiments were noisy and results varied; gains differed by experience |
| Enterprise developer survey (GitHub with Wakefield Research, published August 20, 2024, updated April 15, 2025) | 2,000 non-student, non-manager respondents at companies with 1,000+ employees in the U.S., Brazil, Germany, and India | Self-reported use of AI coding tools at work | More than 97% had used them at work at some point | Measures reach, not frequency or output |
The two headline percentages should not be averaged or quoted as if they measured the same thing. One timed a single task; the other counted completed tasks across ordinary company work. Both describe tools as they were when the work was done. Assistants and underlying models change quickly, so a 2023 result describes that period’s tool, not the one on your desktop today.
What does AI change about writing code?
The clearest picture comes from what developers report doing differently, supplemented by an organizational study. Reported experience is not measured output, and the difference matters for how much weight each claim can carry.
Recommended Free Tools
Adoption is broad; frequency is not measured
The 2024 GitHub survey asked 2,000 developers about their use of AI coding tools, with 500 each in the United States, Brazil, Germany, and India. More than 97% said they had used these tools at work at some point. That figure shows reach. The survey did not ask how often respondents used the tools, and it did not establish that company-wide use was approved or routine.
What developers say the tools help with
- Understanding and adopting code: across the four surveyed markets, 60–71% said AI tools made it easier to adopt a programming language or understand an existing codebase.
- Test generation: more than 98% said their organizations had experimented with AI coding tools for generating tests.
- Quality and saved time: the survey also recorded perceptions about code quality and how developers used time they saved. These are responses, not independent code-quality audits.
AI-generated code and tests still need human review before anyone relies on them.
Where the work shifts: debugging, understanding, and oversight
Anthropic’s December 2, 2025 workplace study drew on a survey of 132 of its own engineers and researchers, 53 interviews, and an examination of how staff used Claude Code. Respondents described using Claude for debugging and understanding code, and reported changes in productivity and in the breadth of work they took on. The same respondents raised concerns about keeping their technical expertise, supervising model output, collaboration, and job security.
Rank #3
The study’s limit is central to reading it. Anthropic’s engineers had early access to advanced tools and work in a relatively stable field. The findings describe that group, not developers generally.
The surrounding system shapes the result
Google’s DORA 2025 report, drawing on more than 100 hours of qualitative data and survey responses from nearly 5,000 technology professionals worldwide, describes AI as an amplifier. It magnifies what an organization already does well and what already goes wrong. The framing implies that a team with weak testing or unclear ownership may see those weaknesses magnified rather than fixed. The assistant is one input into a delivery system, and that system’s review, testing, and planning practices shape what the assistant changes.
Is AI going to replace software developers?
Not on the evidence available so far. A claim that AI will replace developers is a forecast, and the labor-market data we have is preliminary and mixed.
What the employment data shows
The Federal Reserve Board working paper “AI and Coder Employment: Compiling the Evidence,” published as a preliminary paper in March 2026, links occupational data to labor-market data. It finds that coder employment kept growing, but far more slowly than before 2022. The authors report that their industry-level controls do not account for the slowdown. The paper describes an occupation-specific shock around the arrival of ChatGPT, but it is circulated to invite discussion. It does not produce a definitive estimate that AI eliminated a specific number of developer jobs. Slower growth is not the same as job losses, and the paper does not claim otherwise.
The cross-sector picture
The International Labour Organization’s June 1, 2026 review, “The impact of GenAI on jobs, productivity and work organization: a review of the empirical evidence,” covers experiments, firm data, platform studies, and worker surveys across several countries. It concludes that large-scale displacement remains limited in the evidence it reviewed. It also flags risks, including fewer entry opportunities for younger workers and changes to how work is organized and to job quality. Because the review spans all sectors, it is context for software work, not a developer-specific forecast.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →How to read a jobs claim
- Check the outcome. Employment levels, employment growth, hiring of new entrants, and changes in job tasks are different measures and can move in different directions.
- Check the causal claim. A finding that growth changed around a date is not the same as one that isolates AI’s effect from other forces.
- Check whether it is a forecast. Projections about future displacement are not observed outcomes.
GitHub’s COO, Kyle Daigle, has written: “AI doesn’t replace human jobs—it frees up time for human creativity.” That is an executive’s opinion in a GitHub survey article. It is not an independent finding about employment, and it should be read as a view.
Best Value
Will learning to code still matter?
None of these studies followed developers’ careers over years, so the long-term question cannot be answered directly. The evidence bears on it indirectly, through who gained the most from the tools and what developers say they worry about.
Less experienced developers gained the most in one study
In the three-company field study, less experienced developers adopted AI tools at higher rates and showed larger productivity gains during the measurement period. That does not show experience has become less valuable. The study also does not measure whether those early gains last as developers’ skills develop.
Skill erosion and supervision are open questions
Anthropic’s respondents voiced concern about maintaining technical expertise and supervising model output. The supervision concern is practical as well as theoretical: reviewing output requires judging whether it is correct. The evidence does not show whether heavy reliance on assistants erodes skills over time. That remains an open question that none of the studies above were designed to resolve.
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 minutePractical habits the evidence supports
The following steps follow from the findings above. They are reasonable responses to the evidence, not tested methods for protecting skills.
Quick Recap
- Review AI-generated code the way you would review a colleague’s change, before it is merged.
- Use assistants most on tasks you could already check yourself, so you can tell when the output is wrong.
- Periodically complete a task without assistance to see where your own skills stand.
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.
