At 2000 PR/mo, assuming a "standard" 8 hour per day, 5 days a week workweek with no time factored for lunch, meetings, breaks, or PTO... literally all they do for 8 hours a day, 5 days a week, is submitting PRs. That works out to roughly 5 minutes to slop, review, and document a single PR, approx 92 PRs per work day. That tells me they aren't doing shit.
I suspect that an ever increasing number of tickets being raised are being raised by agents themselves, nitpicking and being unable to deal with the idea of implementations having trade-offs.
It doesn't take 5 minutes to prompt claude, "Please pick up Ticket #1234567".
With modern models, you rarely need much more than that. Perhaps checking in an hour later with a quick prompt, "Progress report?" if it's still working on it.
Claude having written the ticket in the first place, defined acceptance criteria. Perhaps a human has skimmed it for a go/no-go decision, perhaps not.
The point is that at that scale you can't humanly read the code, so you need to define verification strategies that work for the machine.
Precisely so that you're not just running on pure vibes.
While I suspect your point about the value/quality of the work at 2000 PRs/month is directionally correct, isn’t their entire take that they’re no longer micromanaging the PRs at all? So talking about how much time they commit to each one doesn’t make much sense. It’s a bit like looking at a modern car and saying “haha how will they even get the horses to pull this?” or maybe “how do these developers know the compiler isn’t using GOTO statements underneath?”.
Now, are those PRs doing useless work? Are they introducing unnecessary risks or trade offs? Are they building towards something impossible to understand or that will fall apart under its own sloppy weight?
Those seem more like the right questions to me, in the long run, and I suspect that’s what you really have in mind. Because if the answers are no, then why wouldn’t you be doing as many PRs as possible?