I just wrote some code that can positively affect our customers, and I’m motivated to release it as quickly as possible. I need your help but you are busy and motivated to continue working on your own code. I call this conflict The Pull Request Paradox.
This problem is not theoretical - it affects most developers every day. The average pull request takes 4 days to merge from when it's opened and half of that time is idle time. Which means every PR sits idle for two days on average! That idle time reduces our code quality, kills our flow, and makes it really hard to plan our sprints accurately.
In this talk I'm sharing:
- New ideas to merge your PRs faster based on analysis of 733K PRs from 26K developers
- Why asynchronous is NOT better than synchronous when it comes to PR code reviews
- Context you can add to your pull requests to get it reviewed by your team 5X faster
- How idle time in PRs reduces situational awareness and increases cognitive load
- Why the time of day you open your pull request affects how quickly you merge
This session is presented by LinearB.
