初步的人工智能影响纵向研究数据
Preliminary data from a longitudinal AI impact study

原始链接: https://newsletter.getdx.com/p/ai-productivity-gains-are-10-not

## 工程赋能 - AI 与生产力更新 本周的工程赋能简报关注 AI 对开发者生产力的*实际*影响。尽管有炒作称收益可达 2-3 倍,但一项 DX 研究分析了 40 家公司一年的数据,显示**拉取请求处理量**的增幅较为适中,为 **9.97%**,同时 **AI 使用率上升了 65%**。 这与工程领导的反馈一致,他们报告的收益通常在 8-12% 之间。关键要点是:**编码并非主要的瓶颈**。开发者表示 AI 使任务*略微*更容易,但仍需花费大量时间进行规划、对齐、审查和其他非编码活动。 该研究将继续调查为什么有些团队比其他团队受益更多,旨在为领导者提供见解,以最大限度地发挥 AI 的潜力。3 月 19 日将举行与 Abi 的现场问答环节,进一步讨论这些话题。

## AI 与开发者生产力:初步观察 近期一项纵向研究(getdx.com)表明,AI 对开发者生产力的影响,以拉取请求 (PR) 的吞吐量衡量,目前尚属边缘化——大约增加了 10%。虽然看似积极,但评论员强调效应量很重要,这种增长可能在统计噪声范围内。 讨论强调,PR 吞吐量并非衡量整体生产力的可靠指标,尤其是在需要仔细向后兼容的成熟项目中。许多人认为,AI 最大的收益将来自于增强高级任务,而不仅仅是加快编码速度。一些人认为,AI 甚至可能通过放大繁琐工作或引入需要返工的错误来*降低*生产力。 一个关键点是 AI 模型正在快速发展;最近的进步,如 Opus 4.5,似乎显著提升了能力,这表明早期的研究可能已经过时。最终,共识是,虽然 AI 是一种强大的*力量倍增器*,但其影响很大程度上取决于*如何*使用它,以及它是否解决了真正的组织瓶颈,而不是简单地加速现有流程。实现实质性收益的潜力仍然存在,但实现这些收益需要调整工作流程并专注于战略应用。
相关文章

原文

Welcome to the latest issue of Engineering Enablement, a weekly newsletter sharing research and perspectives on developer productivity.

🗓 Join Abi on March 19th for a live Q&A session. He will address some of the more pressing questions we’ve received around measuring AI impact, the impact of tool choice, and more. Register here.

Social media and vendor marketing have set high expectations for AI, suggesting as much as 2-3x productivity gains. But from the data we’re seeing, the reality on the ground is far more modest.

At DX, we’re currently conducting a longitudinal study to measure the long-term impact of AI adoption on key engineering productivity metrics. As part of this study, we analyzed data from 40 companies between November 2024 through February 2026 to track whether teams are shipping more pull requests as AI adoption increases.

We found that, during this time, AI usage increased significantly—by an average 65%. However, PR throughput only increased by 9.97%.

Note: This figure is particularly robust because we’ve filtered out potential gamification effects by excluding teams that set PR throughput targets for individual engineers, which could drive metric inflation rather than genuine output.

A ~10% gain is consistent with what we’re hearing from engineering leaders more broadly: most organizations are landing in the 8–12% range. It is a real improvement, but it’s a long way from the 2–3x gains many executives and boards have come to expect. AI is moving the needle, but leaders may need to reset expectations internally.

To understand what’s driving this, we spoke with developers across several of these organizations. The explanation we heard most consistently: writing code was never the bottleneck.

As one senior developer put it: “The easy tasks are a little easier. The tedious tasks are a little less annoying. A four-day task might take three. But that doesn’t mean I’m shipping 3x more PRs.”

AI may be accelerating the coding portion of the job. But coding represents a relatively small slice of how engineers actually spend their time. Planning, alignment, scoping, code review, and handoffs—the human parts of the SDLC—remain largely untouched.

We’re continuing to investigate the long-term effects of AI in engineering teams. The full study will explore why some teams are capturing more of the upside than others, and what leaders can do to close that gap. More to come.

This week’s featured DevProd job openings. See more open roles here.

That’s it for this week. Thanks for reading.

Share

联系我们 contact @ memedata.com