“The biggest thing that maybe happened between last year and this year was it suddenly became very clear that code review is a bottleneck, especially once people got really AI-pilled and the velocity on generation became so high that you could in theory put up 30-plus PRs a day, and then what? At what point do you decide that you either have to institute yourself and put yourself in the middle as some way to gate and review things in the traditional way, but then you're literally the constraint, you're the choke point of the velocity, and that's not good? Then what was the point of generating at scale?”

yeah exactly right yeah there we go to the merge queue and beyond um yeah this is a yeah a love letter of sorts to modern gen tech code review um yeah i think that the the the biggest thing that maybe happened between last year and this year was just it suddenly became very clear that code review is a bottleneck especially once you people got really AI pilled and the velocity on generation became so high that you could in theory like put up 30 plus PRs a day and then what? At what point do you decide that you either have to institute yourself and put yourself in the middle as some way to gate and review things in the traditional way, but then you're literally the constraint, you're the choke point of the velocity and that's not good, right? Then what was the point of generating at scale? Or you say, well, how do we maybe get the best of both worlds where we're instituting ourselves enough that we have trust in what's getting merged, but we're also able to kind of like merge it scale, but we're also not kind of freewheeling it here and anything goes. So a lot of, I think what I want to touch on here is just that middle ground, right? Which is like, there is a class of problems that if you've put in thoughtful design into your agent readiness, you've put in thoughtful design around your verifiability, there's a class of problems that you can feel comfortable, you know, some percentage…