Remix.run Logo
▲ xnorswap an hour ago

Slopping out 2k+ PRs/mo while also claiming to reduce defect rates.

That seems like something to pay attention to, even if you prefer to treat it as a cautionary tale with your popcorn at the ready for when you expect it all comes crashing down.

▲rolosa 33 minutes ago | parent [-]

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.

▲xnorswap 13 minutes ago | parent [-]

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.