How to Create PRs That Get Merged The Same Day

https://is1-ssl.mzstatic.com/image/thumb/Podcasts221/v4/07/85/33/078533b5-bd05-6aa4-d93c-c87e26081cfc/mza_9604738249533254209.jpg/600x600bb.jpg

NO SILVER BULLET

Three Dots Labs

10 episodes

5 days ago

Based on nearly 20 years of working together on various projects, we discuss when it makes sense to move fast rather than aim for perfect code, and how to avoid technical debt that can kill your project. We focus on making mindful engineering decisions instead of blindly following rules like “always do X” or “never do Y”. Different situations need different approaches to code quality.

Technology

RSS

All content for NO SILVER BULLET is the property of Three Dots Labs and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.

Technology

https://d3t3ozftmdmh3i.cloudfront.net/staging/podcast_uploaded_nologo/43392592/43392592-1744901791382-4acfb7879abd4.jpg

How to Create PRs That Get Merged The Same Day

NO SILVER BULLET

1 hour 27 minutes 44 seconds

4 months ago

How to Create PRs That Get Merged The Same Day

Full episode notes: https://threedots.tech/episode/prs-that-get-merged-the-same-day/

Quick takeaways

Prioritize reviews over new work - treat PRs as work that’s almost done and needs to be pushed to production quickly
Big PRs create a dead loop - when reviews take ages, developers make even bigger PRs to avoid multiple long waits
Knowledge sharing is the hidden benefit - code reviews aren’t just gatekeeping, they spread understanding of how things work across the team
One-day cycle time is possible - start work in the morning and merge by end of day with proper team culture and practices
Split work vertically and horizontally - break features into small slices and layers that multiple people can implement in parallel

In this episode, we discuss how to make code reviews fast and effective by keeping pull requests small.

We explore why big PRs are problematic, what causes them, and practical strategies to create PRs that can be merged within a day.

Instead of waiting days for reviews with 200 comments, we focus on techniques that help teams achieve smooth, fast review cycles where work flows quickly from code to production.

Introduction