A working mental model for React Server Components
After a year of shipping with RSC in production, here's the framing that finally made it click for my team.
Server Components confused everyone on my team for the first month. Here's the framing that finally got us all on the same page.
Server is the default; client is an opt-in
Flip the mental model. By default, your component runs on the server, has zero JS cost on the client, and can talk to your data layer directly. You only opt into the client when you need interactivity.
Tagged
Keep reading
All posts →Shipping SSR on Next.js: how I cut page loads by 35%
A pragmatic walk-through of the rendering, caching and image strategies behind a real CMS revamp — including the trade-offs nobody talks about.
Docker + Azure DevOps: a CI/CD recipe that halves release time
The exact pipeline structure, caching tricks and image layering rules that took our deploys from 18 minutes to under 9.
Design systems with Tailwind: lessons from real-world products
Tokens, primitives, and the discipline it takes to keep a Tailwind codebase from devolving into utility-class soup.