Stop Using Pull Requests
The article critiques the use of pull requests in software development, arguing that they are ill-suited for trusted teams. It highlights that pull requests were designed for open source projects and often lead to inefficiencies and a false sense of quality. The author proposes alternatives like Test-Driven Development and Trunk-Based Development to enhance software quality and team collaboration.
- ▪Pull requests were originally created for open source contributions from untrusted individuals.
- ▪Research indicates that the primary benefit of code reviews is knowledge transfer, not bug detection.
- ▪Asynchronous pull request workflows can cause significant delays, with some organizations spending thousands of hours waiting on unreviewed code.
Opening excerpt (first ~120 words) tap to expand
Stop Using Pull RequestsYour team’s code review process is probably an expensive illusion of quality. Here’s what the evidence says, and what to do instead.Andrea LaforgiaMar 19, 202622719Share“Inspection is too late. The quality, good or bad, is already in the product. Cease dependence on inspection to achieve quality. Eliminate the need for inspection on a mass basis by building quality into the product in the first place.”-- W. Edwards Deming, Out of the Crisis (1982)AbstractPull requests have become the default code review mechanism in software teams everywhere. But the pull request was invented for open source projects, where strangers contribute code to repositories maintained by people who don’t know them.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Lobsters.
Discussion
0 commentsMore from Lobsters
