The Programmer's Guide to Deep Work
What the research does and does not say, and the small environmental tweaks that actually compound over months.
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
Tools I Use Every Day as a Staff Engineer
A calm, unsponsored list of software that has earned its place on my machine over the last several years.
A Letter to My Junior Self
The handful of habits and attitudes I wish someone had pushed me to adopt in my first two years of work.
The Art of Walking Away From Technical Debt
Not every shortcut deserves a rewrite. Here is how to tell which debts to pay down and which to simply retire.