Monorepos Are Not the Problem
Build graphs, caching, and ownership boundaries are. A monorepo just makes your existing problems visible.
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
The Case Against Global State
Half of your Redux store is server cache in disguise. The other half is probably URL state.
Shipping a Design System Nobody Hates
Why the component library is the easy part, and the governance is the hard part you will keep putting off.
Handling Money in JavaScript Safely
Integer cents, decimal libraries, and the one-line rounding bug that cost us a remarkably long afternoon.