Minions – Stripe's Coding Agents Part 2
31 points
1 hour ago
| 6 comments
| stripe.dev
| HN
testfrequency
51 minutes ago
[-]
How is this already #1 on the front page with 12 upvotes and 9 comments…

The article doesn’t reveal much. It feels like a fluff piece, and I can’t comprehend what the goal of sharing “we use AI agents” means for the dev community, with little to no examples to share. For a “dev” micro blog, this feels very lackluster. Maybe the Minion could have helped with the technical docs?

EDIT: slightly adjusts tinfoil hat minutes later it’s at #6

reply
BiteCode_dev
24 minutes ago
[-]
Likely they have whitelisted domaine names that go straight to the home page. Would make sense to put all Y combinator ex and new startup sites.

Marketting is a major goal of HN after all.

reply
3rodents
1 hour ago
[-]
Are any companies doing this sharing the code being produced or some example Pull Requests? I am wondering if a lot of the human review is substantive or rubber stamping - as we see with long Pull Requests from humans. I know I would half-ass a review of a PR containing lots of robot code. I assume stripe has higher standards than me but would be nice to see some real world examples.
reply
fnord123
1 hour ago
[-]
On thing that troubles me is that code reviews are also an educational moment for seniors teaching juniors as well as an opportunity for people who know a system to point out otherwise undocumented constraints of the system. If people slack on reviews with the agent it means these other externalities suffer.

Are being handling this at all? Is it no longer needed because it gets rolled into AGENTS.md?

reply
blitzar
1 hour ago
[-]
I find working with Ai a lot like working with a junior employee... with the junior employee they learn and get better (skill level and at dealing with me) but with Ai the mentoring lessons reset once you type /clear

Skills are a positive development for task preferences, agents.md for high level context, but a lot of the time its just easier to do things the way your Ai wants.

reply
nottorp
26 minutes ago
[-]
Hey can they ask their coding agents to support 3D secure, so I can pay with EU emitted credit cards on the few US sites I'm interested in?
reply
rco8786
52 minutes ago
[-]
I'm sure there are lots of Stripe engineers that cruise the comments here. Anyone care to provide some color on how this is actually working? It's not a secret that agents can produce tons and tons of code on their own. But is this code being shipped? Maintained? Reviewed?
reply
dakolli
36 minutes ago
[-]
The few guys who they haven't laid off are too busy reviewing and being overworked, doing the work of 10 to scroll HN. Gotta get their boss another boat, AI is so awesome!
reply
gas9S9zw3P9c
1 hour ago
[-]
Where is the detail? Examples? Something concrete? I don't think it is, but it does read like LLM generated content marketing. Lots of generic statements everyone knows. Yes, dev environments are helpful. Have been for 20 years. Yes, context and rules are important for agents. Surprise.

TLDR "look we use AI at Stripe too, come work here"

reply
vbs_redlof
1 hour ago
[-]
Good to see we're vibe coding critical financial infrastructure. Progress is being made.

Next up: let's vibe code a pacemaker.

reply
ndr
29 minutes ago
[-]
Soon indeed. From today:

> Cardiologist wins 3rd place at Anthropic's hackathon.

https://x.com/trajektoriePL/status/2024774752116658539

reply
trevorhinesley
1 hour ago
[-]
The glass-half-full here is it’s an incredible signal that one of the largest financial gateways in the world is _able_ to do this with current capabilities.

Personally, this is exciting.

reply
handfuloflight
55 minutes ago
[-]
They are enforcing rigor, on agents, the same way they would on humans. Do people think Stripe's engineering team would have been able to progress if each individual (human | machine) employee was not under harness and guardrail, and just wrote code willy nilly according to their whims? Vibe coding is whimsical, agentic engineering is re-applying what brought and brings rigor to software engineering in general, just to LLM outputs. Of course, it's not only that and there are novel problem spaces.
reply
dakolli
35 minutes ago
[-]
bot ass comment.
reply
handfuloflight
24 minutes ago
[-]
You're absolutely wrong! @dang, I really did write each letter by hand!

Lt. Dang, ice cream!

reply
kypro
56 minutes ago
[-]
Exactly, 1000 PRs per week probably equates to around ~100 engineers worth of output.

Hard to do an exact ROI, but they're probably saving something like $20,000,000+ / year from not having to hire engineers to do this work.

reply
qudat
28 minutes ago
[-]
They still need someone to review and hopefully QA every PR. I doubt it’s saving much time except maybe the initial debug pass of building human context of the problem. The real benefit here is the ability for the human swe to quickly context switch between problems and domains.

But again: the agent can only move as fast as we can review code.

reply
handfuloflight
58 minutes ago
[-]
Vibe coders do not know what linting is.
reply