SUMMARYA Harvard University study by Fiona Chen and James Stratton analyzed engineering activity at more than 700 software firms using Jellyfish data covering 700,000 employees and 300 million work events from 2021 through March 2026. The findings show AI coding tools speed up code generation, but extra human review absorbs those gains, with longer review cycles, more pull request revisions, and no clear increase in software output or employment reduction.

Here, let me just... yeah, can I lend you a hand here?
Getty Images
arstechnica.com
Here, let me just... yeah, can I lend you a hand here?

Anyone who has even tangentially associated with computer programming knows that modern AI coding assistants and agents can be incredibly efficient at generating huge amounts of functional code. But coders making use of those tools also know better than to trust the accuracy of that code, meaning substantial effort needs to be spent reviewing any AI-generated output.

A recent study of actual coding practices across hundreds of firms finds that human code review forms a significant "bottleneck" for the overall efficiency of AI coding tools, resulting in "little evidence that firms increase software output or reduce employment" by using them. Any efficiency increased during the actual coding phase, the study authors find, is "absorbed by downstream constraints in the production process"; as "the code review process significantly increases in length, pull requests are more likely to require revisions, and reviewers leave more comments."

Cut once, measure twice

To come to these conclusions, Harvard University researchers Fiona Chen and James Stratton made use of aggregated analytics data from Jellyfish, which measures the granular output of engineering teams. That data encompasses 300 million individual "work events" (e.g., commits and pull requests) and issue management software data across more than 700,000 employees at over 700 relevant software development firms from 2021 through March of 2026.

Read full article