Stripe Dev Blog

Recently I added sounds to a website that fall into this non-essential but experience enhancing (imo) category. I've had somewhat mixed response to this, from total annoyance to utter delight. I'm really not sure what the best approach is to take with sound on the web. edit: Sounds are present when opening the console, or dragging a canvas around https://stripe.dev/

We can only guess what products you use, but I'll take a stab by naming some big ones: Spotify - https://techcrunch.com/2026/02/12/spotify-says-its-best-developers-hav… Netflix - https://www.cnbc.com/2025/10/22/netflix-all-in-on-leveraging-ai-in-its… Stripe - https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-age… Discord - https://discord.com/blog/developing-rapidly-with-generative-ai

I don't know if we're all 10x'ing but our entire org is shipping PRs using an in-house framework akin to Stripe's Minions [1] and many of those PRs are generated from Slack. We definitely have work to do on the latter part of the SDLC to have more confidence in these changes but we can still rely on the existing observability layer to make sure things are working as expected. Another commenter mentioned that Docker, git, etc. were all tools that greatly enhanced productivity and coding agents are just another tool that does that. I would agree, but argue that it's more impactful than all of those tools combined. [1] https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-age…

Very cool. Reminds me of the Stripe developers site. https://stripe.dev/

I admire and blame David Carson for this. It requires no skill to make something legible. The point of art isn't to be legible, it's to pull eyeballs (and sales) or send a message. If something is pleasing to everyone, it stands out to nobody. Every junior designer will create a very clear website. And there's no harm in hiring junior designers if you want that. More experienced ones will try to annoy some to attract others. I have no idea what's going on with https://stripe.dev for example. It's beautiful. There's a pointless fractal in the corner. The link to Stack Overflow is equally pointless. But in the end, I get the impression that Stripe does some precision shit which is what I want for a payment gateway.

So this seems like a good time to tell my Stripe story. Let me preface this by saying I attempted to move to a different card processor late last year/early this year and despite 100+ hours of coding to fully integrate with them (and add features that were missing compared to our Stripe integration) I had to drop them due to what can only be described as lies about their rates (yes, I should have gotten this in writing instead of just over the phone but I was naive). All that said I had <1 week to switch back to Stripe before preorders started for the event and it was a breeze. Stripe has it's problems but I still think they are the best game in town. Now for my Stripe issue. Around the time I dropped the other payment processor I bought some Stripe M2 readers (Part of "Stripe Terminal" for in-person payments). At the same time I purchased a "Stripe Terminal Test Card" to use in the test environment. They have a simulated reader but I always prefer to use the same hardware as production to get a better feel for how it all works. The readers arrived and so did the card but for some reason I could not get the card to read, I kept getting back an error code of "6" [0] telling me that the card could not be read. If I scanned a real card it would scan and then fail when trying to auth the payment (understandable, I was in the "test" environment) but to me this proved the reader was working. I did some testing in "live" and all my cards were read/charged without issue. I opened…

Very readable and interesting outlook on the current developments in the market. Also really interesting to show that a company which started with a more technical product: https://stripe.dev/blog/payment-api-design is now exposing to their investors about how the world GDP and economics are expected to be developing in the coming years. The vision in the document seems to make sense, is clear and they clearly invest in this trajectory themselves.

This was one of the key insights in Stripe's explanations about Minions[0], their autonomous agent system; in-between non-deterministic LLM work they had deterministic nodes that handled quality assurance and so on in order to not leave those types of things to the LLMs. 0 - https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-age…

Associated blog post: https://stripe.dev/blog/production-ready-dev-stack-from-terminal

They mention "Why did we build it ourselves" in the part1 series: https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-age… 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.

For credit card and bank accounts, Stripe Elements has some battle-tested React inputs: https://stripe.dev/elements-examples/