Git Workflows Reconsidered
Trunk-based, GitFlow, and the handful of questions that actually decide which one fits your team.
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
Why Conventional Commits Are Worth the Overhead
A small discipline with outsized payoffs in changelogs, release automation, and pull request review velocity.
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.
Publishing a TypeScript Package in 2026
Dual ESM/CJS, `exports` fields, and the minimum setup that will not embarrass you on npm next week.