Drawing Boundaries in a Fullstack App
Where the server ends, where the client begins, and how to stop your types from smearing across the line.
This is placeholder body copy. In a real post there would be an argument here, built one paragraph at a time, with the kind of small detours that make a technical essay feel like it was written by an actual human.
The repository this page lives in exists to demonstrate behavior of the Next.js router, so the content is intentionally boring. Any similarity to real insight is entirely coincidental, if occasionally welcome.
If you are reading this from a prefetch-triggered hover, congratulations, the link worked. If you are reading it after a full navigation, that also counts, and you have learned something about how caches behave under load.
More posts
Unit Tests Are Not a Replacement for Thought
They catch regressions, not design mistakes. Here is the kind of thinking that still has to happen up front.
E2E Testing That Does Not Flake
Deterministic selectors, network stubbing, and the small investments that turn a red pipeline back to green.
A Sober Look at AI Code Assistants
Where they genuinely help, where they introduce silent regressions, and how senior engineers actually use them.