Semantic Versioning Is a Social Contract
Why SemVer only works when publishers and consumers agree on what "breaking" means, and what to do when they do not.
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
Publishing a TypeScript Package in 2026
Dual ESM/CJS, `exports` fields, and the minimum setup that will not embarrass you on npm next week.
The Small Joy of Finishing Side Projects
A nudge toward shipping the imperfect version tonight rather than rewriting the landing page for another weekend.
Reading Papers Without Going Insane
A practical workflow for working engineers who want to stay current with research without pretending to be academics.