Discover · simplecast.com

Engineering's hidden bottleneck: pull requests

The Stack Overflow Podcast simplecast.com

This is what was read here when it was published. simplecast.com no longer carries it in what it publishes now.

With companies taking a long look at developer experience, it’s time to turn that attention on the humble pull request. The folks at LinearB took a look at a million PRs — four million review cycles involving around 25,000 developers — and found that it takes about five days to get through a review and merge the code. CI/CD has done wonders getting deployments down to a day or less; maybe it’s time for continuous merge next.

On this sponsored episode of the podcast, we chat with COO Dan Lines and CEO Ori Keren, co-founders of LinearB, about why PRs are the chokepoint in the software development lifecycle, uncovering and automating the hidden rules of review requests, and their free tool, gitStream, that’ll find the right reviewer for your PR right now.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Names and references

  1. Engineering — person

Named in it

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

More like this

Also from The Stack Overflow Podcast

  1. Trying to get our Arms around AI efficiencysimplecast.com
  2. The pioneering coding tricks that built Doom and Quakesimplecast.com
  3. Agentic search doesn't find pages, it assembles answerssimplecast.com
  4. Customer support is the gnarliest AI problemsimplecast.com
  5. Welcome to life in the chip agesimplecast.com
  6. Oh, your agents need OAuth2, toosimplecast.com