React Server Components, two years in: the patterns that survived
We migrated 4 production apps to RSC. Here's what stuck, what we ripped out, and the data-fetching pattern we'd recommend to a friend.
Engineering deep-dives, retrospectives, and field notes from teams shipping production software. No hot takes, no thought leadership — just what we learned this week.
Eight months running production agents taught us more about LLM failure modes than any benchmark. Here's the eval architecture we use to catch hallucinations before they reach users.
We migrated 4 production apps to RSC. Here's what stuck, what we ripped out, and the data-fetching pattern we'd recommend to a friend.
A client's queries got 40× slower over six months. The culprit wasn't query planning — it was something we'd never thought to monitor.
How we score retrieval quality, response groundedness, and citation accuracy — with a CI pipeline that blocks regressions before merge.
The architecture, OTA update strategy, and crash-monitoring setup we used — plus the three Expo features that genuinely saved us weeks.
The audit framework, the easy wins, and the one architectural change that quietly saved us the most money. Spoiler: it wasn't reserved instances.
An honest retrospective — what worked, what we'd do differently, and the architectural decisions we're still living with (good and bad).