Building a Personal Knowledge Base That Lasts
File formats, folder conventions, and a review cadence that keeps notes useful for longer than a semester.
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
Shell Tricks Every Developer Should Know
A short, opinionated list of incantations that quietly save an hour a week once they become muscle memory.
Git Workflows Reconsidered
Trunk-based, GitFlow, and the handful of questions that actually decide which one fits your team.
Why Conventional Commits Are Worth the Overhead
A small discipline with outsized payoffs in changelogs, release automation, and pull request review velocity.