Deep dives into architecture, AI, infrastructure, and product engineering — written by the people who shipped it, not a content team.
Featured Story
This week's essential read
The one piece from the team worth your full attention.
AI Code Review That Engineers Actually Trust
Most AI review bots get muted within a week. Here's the architecture behind the one our engineers actually keep enabled — and why comment volume was the wrong metric from the start.
Read ArticleExplore Topics
Read by discipline
Nine tracks covering everything we build and think about.
Editor's Picks
Handpicked by the team
Three pieces our engineers keep sending to each other.
Latest Articles
Every article, in order
Search by keyword or narrow down by topic.
AI Code Review That Engineers Actually Trust
Most AI review bots get muted within a week. Here's the architecture behind the one our engineers actually keep enabled — and why comment volume was the wrong metric from the start.
Designing for Failure Domains, Not Just Failures
A single retry policy taught us that "handle the failure" is the wrong question. The right one is "how far should this failure be allowed to travel?"
Rethinking State in Large React Applications
Global state libraries don't fail because they're badly built. They fail because most teams reach for one before asking where the state actually lives.
Shipping Faster With Progressive Delivery
We stopped asking "is this safe to deploy" and started asking "how little blast radius can this deploy have." That shift cut our rollback time from 40 minutes to under 90 seconds.
From Lift-and-Shift to Landing Zones
A lift-and-shift migration gets you to the cloud. It doesn't get you a cloud architecture. Here's what we build instead for clients migrating for real.
The Pragmatic Monolith
We've talked three separate clients out of a microservices rewrite this year. Not because microservices are wrong — because none of them had the problem microservices solve yet.
Building Idempotent APIs at Scale
A retried payment request charged a customer twice. The fix wasn't better error handling — it was accepting that every write endpoint needs to answer "what if this exact request arrives again?"
What Makes a Roadmap Actually Useful
Most roadmaps are read once, at the meeting where they're presented, and never again. Here's the format we switched to that engineers and clients both actually keep open.
A Design System Is a Product, Not a Style Guide
The design systems that get adopted have a roadmap, a changelog, and someone who says no to bad additions. The ones that don't are just a Figma file nobody opens anymore.
Engineering Spotlight
Six ways we tell engineering stories
From Lift-and-Shift to Landing Zones
A lift-and-shift migration gets you to the cloud. It doesn't get you a cloud architecture. Here's what we build instead for clients migrating for real.
Read the storyOne email, every other Friday
Engineering notes, new articles, and things we learned the hard way — no marketing, ever.
Read by 2,400+ engineers. Unsubscribe anytime.
Let's talk
Let's build what's next.
If any of this sounds like the kind of work you want done on your systems, our engineers are the ones who'll actually do it.