undefined | Better HN

0 pointsmenaerus1mo ago0 comments

They mention "Why did we build it ourselves" in the part1 series: https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-...

However, it is also light on material. I would also like to hear more technical details, they're probably intentionally secretive about it.

But I do, however, understand that building an agent that is highly optimized for your own codebase/process is possible. In fact, I am pretty sure many companies do that but it's not yet in the ether.

Otherwise, one of the most interesting bits from the article was

> Over 1,300 Stripe pull requests (up from 1,000 as of Part 1) merged each week are completely minion-produced, human-reviewed, but containing no human-written code.

0 comments

tempest_1mo ago

"human reviewed"

"LGTM..."

I feel like code review is already hard and under done the 'velocity' here is only going to make that worse.

I am also curious how this works when the new crop of junior devs do not have the experience enough to review code but are not getting the experience from writing it.

Time will tell I guess.

menaerusOP1mo ago

Agents can already do the review by themselves. I'd be surprised they review all of the code by hand. They probably can't mention it due to the regulatory of the field itself. But from what I have seen agentic review tools are already between 80th and 90th percentile. Out of randomly picked 10 engineers, it will provide more useful comments than most engineers.

tibbar1mo ago

the problem with LLM code review is that it's good at checking local consistency and minor bugs, but it generally can't tell you if you are solving the wrong problem or if your approach is a bad one for non-technical reasons.

This is an enormous drawback and makes LLM code review more akin to a linter at the moment.

1 more reply

j / k navigate · click thread line to collapse