How Developers Are Actually Using AI at Work in 2026: A Brutally Honest Analysis of 10,000+ PRs, Real Productivity Data, and What Nobody's Talking About
A recent analysis of AI usage in software development reveals that while AI can increase the volume of work, it does not necessarily enhance overall productivity. The study tracked over 10,000 pull requests (PRs) across different workflows, showing that AI agents submitted significantly more PRs but had a much lower merge rate and higher bug introduction rates. The findings suggest that AI's true value lies in opportunity discovery rather than code generation.
- ▪The AI-agent workflow submitted 6.6 times more PRs than the manual workflow but had a merge rate that dropped from 81% to 15%.
- ▪AI-generated PRs received 5.7 times more review comments than manual PRs, indicating issues with context and adherence to project conventions.
- ▪The biggest productivity gain from AI was in identifying opportunities rather than writing code.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/zeroknowledge0x/how-developers-are-actually-using-ai-at-work-in-2026-a-brutally-honest-analysis-of-10000-prs-5fdo |
| Publication time | Sat, 30 May 2026 05:21:23 +0000 |
| Retrieval time | 2026-05-30T05:42:06.163Z |
| Last seen | 2026-05-30T05:42:06.163Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | cAY42nFLPi5q |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3959173) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } zk0x /// ℹ️ Posted on May 30 How Developers Are Actually Using AI at Work in 2026: A Brutally Honest Analysis of 10,000+ PRs, Real Productivity Data, and What Nobody's Talking About #ai #data #discuss #productivity Everyone claims AI makes them 10x more productive. I measured it. The results are more nuanced — and more interesting — than anyone admits.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).