Developers spend only a fraction of their day coding, with the majority of time spent on related non-coding activities like code reviews and meetings.
Pull request cycle time is broken down into coding, pickup, and review phases, with research showing that PRs are idle for about half their lifespan.
PR delays are caused by transition time from handoffs and distraction time from interruptions, both of which increase cognitive load and slow down the entire process.
Pull requests are essential for quality, knowledge sharing, and onboarding junior developers, so the goal is to make the process efficient through a continuous merge mindset.
Improve PR workflows by optimizing communication and context, and by routing PRs into different lanes like 'ship', 'show', or 'ask' based on their complexity.
Keep pull requests small, provide an estimated review time to reduce pickup delays, and use synchronous reviews for complex PRs to save time.
Tools can automate non-coding work like creating Jira tickets from pull requests or allowing PR approvals directly within Slack to reduce friction.
Browser extensions can add context like estimated review time to GitHub, while IDE plugins can warn about potential conflicts before a PR is even created.
Pair programming is a valuable synchronous review option for complex work but is difficult to apply universally, making it another tool for routing decisions.
Sensory-Minds GmbH
Offenbach am Main, Germany
1:01:43Samuel Shaw
28:45Lian Li
24:19Johannes Haux
31:39Rainer Stropek
23:44Sven Amann
23:03Robert Hoffmann
43:00Luka Kladaric
24:31Daniel Tao
.webp?w=240&auto=compress,format)
.png?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
YO IT CONSULTING
YO IT CONSULTING
YO IT CONSULTING
YO IT CONSULTING
YO IT CONSULTING
Thinkbyte Consulting, Inc.
