best-practice development git reading-list

In the world of software delivery, pull requests are at the heart of collaboration between many engineering teams. Yet, while PRs are pivotal for ensuring code quality and fostering collective input, they've also become the leading bottleneck in developer workflows.

Poorly crafted or mismanaged pull requests can spell disaster for productivity. LinearB's Engineering Metrics Benchmarks study analyzed the work of 2,000 dev teams and 4.5 million code branches, and found:

  • The average cycle time for a piece of work (first commit to deployment) is 7 days.

  • Half of all PRs are idle (e.g., no one is actively working on them) for at least 50% of their lifespan.

  • Cycle time and idle time doubled for pull requests of 200 lines of code compared to pull requests with 100 lines of code.

Having pinpointed this significant dip in developer productivity, researchers have uncovered the root of these subpar performance indicators.

Based on qualitative and quantitative analyses, developers and data scientists have identified four primary issues in PR management and 11 common types of pull requests that are particularly detrimental to workflow efficiency.

continue reading on devinterrupted.substack.com

⚠️ This post links to an external website. ⚠️

You might also like:

If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.