Strip out the Iran inflation picture and the Fed would still be hiking. The US economy is strong enough on its own to warrant it, because that is what central banks do. They hike when things get hot. The inflation backdrop just makes the Fed more comfortable that the hike will not do much damage.

Stripe Data Pipeline now supports real-time sync to Lakebase Postgres! With updates arriving within seconds, apps can use SQL to manage feature access, display billing details, and deliver personalized offers.

Stripe-owned Privy now supports XRP Ledger wallets after a partnership with @Ripple, letting developers create wallets and sign $XRP and RLUSD transactions in their apps. Full BSCN Daily episode:

Stripe is making more of its services available through CLIs and AI agents, and I keep seeing predictions that SaaS dashboards are on their way out. I'm not convinced. Plenty of paying customers still want to log in, see what's happening and click a few buttons. I reckon we'll need both for quite some time.

Stripe’s 1st employee @darraghbuckley on how it held its high agency culture longer than Facebook, Google, or Microsoft: "I enjoy working in high-empowerment cultures, and with people who do too. High empowerment means the ability to wander and make the change you need to build the product. There are prerequisites. You have to hire well. And you have to trust the people you hire. And trust that they trust you to go effect that change. It also means you can't silo too strictly. You let a compliance person wander into engineering, and an engineering person into compliance. More than allow it, you expect it. Stripe was very good at this for many years. Stripe maintained it to a higher headcount than Facebook did. Facebook maintained it higher than Google. Google higher than Microsoft. I'd hope at Increase we can maintain it to an even larger headcount."

Stripe's first employee @darraghbuckley on the early habit that set it apart: "The differential characteristic early on was a culture of long-form written communication. Writing it down. That wasn't as common in 2010 as it is now. The reason you wrote long-form was that it helped you learn. It forced you to put your ideas down as falsifiable statements. You'd expose all of your logic to someone else, and they'd be able to point out the parts that were more or less shaky."

Stripe’s 1st employee @darraghbuckley on why banking infrastructure is still a huge problem: "While building Stripe, we built on top of a cohort of US banks. And you could always tell we were a bit of an awkward duck, always wearing someone else's shoes. Something felt off. For example, Stripe never disbursed to merchants by wire. A natural way to move large amounts of money is a wire. But Stripe was hesitant. Because when a wire failed, we'd get an email from the bank partner saying we couldn't deliver this, go repair it. It's hard to build a product you're proud of on top of manual flows like that. There were dozens of cases like these. “Oh, that data element? We don't pass it through. Why would you want it?” You knew you were building on someone else's product. There was a stone in your shoe, and you were trying to explain why it was so annoying to someone who couldn't see it. No fault on them. The product was built for someone else, and you weren't the target user. Anytime you see a product that almost fits, with so much built on top of it, one of us should go back and redo the foundations. That's what prompted me to start @IncreaseDev."