1. Blast Radius
The speaker evaluates pull requests based on their blast radius, where touching a database creates a huge blast radius, while a minor frontend tweak outside the design system has a very small one.
Hear it at 0:04 →Engineering video
0:58 · 20 October 2026
i dont review most ai pull requests
Key concepts in this video:
Transcript
The result of this will be a lot of pull requests, and a lot of people are talking about code review or not. I'll be honest with you, I only give you based on the blast radius and the services affected. And if the blast radius is very small and it only affects one service, then I would just have you I merging it. What do we mean by blast radius? Well, you can imagine it's almost as a layer. If it touches the database, that's a huge blast radius. If it's just a tweak on a front-end component, that's not even in the design system, that's a very small blast radius. If you go into the design system
because it affects the whole thing, then it's a bigger blast radius. And right now, just to demo a bit, my mornings look like this. So, I wake up to a lot of pull requests created by agents, and depending on the ticket that I look at, then I'll decide to either merge it or not. And by the way, this was just yesterday, right? A lot of those. We usually average with the software factory 10 to 20 PRs per developer in a day.