On-Call Playbooks Worth Writing
The shape of a runbook that helps a sleepy human, not a confident one, and why the difference matters.
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
Incident Response Without Blame
How to run a post-incident review that produces durable learning instead of a lingering bad taste.
Architecting for Graceful Degradation
Designing systems where the first failure is a shrug, not a full outage that trends on social media.
The Underrated Power of Feature Branches
Why the shape of your branching strategy quietly determines the shape of the conversations your team has.