The study unfortunately looks only at individual productivity, not any org gains, and the big claim in the PDF is that adopters "merge roughly 24% more pull requests" over a four month period. not exactly headline-making material. There's no data in the paper whether those 24% extra pull requests actually added anything more valuable or not.
To me the biggest gain I see is that you take the programmers out of the loop. Instead of formulating your ideas to start a project and then acquiring the resources to do a single iteration on it which may take months if not years, now many specialists "just do it" and do several such iterations in a single day. Afterwards they may still go the ordinary route via programmers but on a completely different level and a lot of fruitless work is frontloaded and 100x cheaper. This doesn't show up in any such statistic.
So, the question is not "Does it make our programmers more productive?" but "Does it make our organization faster?".
What kind of metric would you trust for measuring organization gains?
Yeah welcome to the state of the art in measuring AI impact. I have contacts at a few different larger tech companies that are fully AI pilled (the one I work at included) and every single one has forgotten the last 50 years of lessons in measuring dev productivity and hyperfocused on PR throughput and token usage.
Fun fact: all the data I've seen suggests at most a 50% uplift in those metrics. And that's at the top percentiles. Its very clear that the already high performers see the greatest uplift but anyone in that meaty middle will only see incremental gains.
To be fair they do acknowledge this directly in the abstract. Kinda hard to have a good heuristic for this stuff, what would you propose?
more features doesn't mean anything if they don't translate into economic value, refactoring prs and dependency updates are easily automated now and it saves alot of productivity, but if you compare the costs and economic value gained it might not actually justify enterprise token spending.
Highly doubt. Pace for merging requests have not improved and teams at MSFT are terrible at reviewing said PRs. Longer PRs and more frequent requests were clearly creating more friction.
Dependabot PR merges :rocket: :rocket:
My personal experience was that I saw AI adopters opening and merging more PRs but I also spent more of my day reviewing PRs than I did in the past, in order to keep up with the flood of new stuff. Reconcile that with MSFT's repeated layoffs however you like.
24% of increased productivity (yes, this is assuming of course that the “proxy” of merged PRs reflects productivity) is actually a pretty big deal. Given the salary of developers, this translates to tens of thousands of dollars per year, per developer.
My guess is they used # of PRs as a measure as it’s easy to obtain, while other measures are hard, may be due to other factors, etc.
FWIW I saw a similar number for myself, around 30% more PRs in the last 6 months, compared to the 6 months before that (I picked up agentic coding around at the start of the year). And a similar increase for closed issues.
In my case this clearly doesn’t translate to as much value for the organization, or rather, it’s hard to say, as many of those PRs were things I wouldn’t even have done without AI support. This means they were low priority. However, many were of the cleanup/refactor type, so they might result in speedups later.