Welcome to the notebook.
This is where I keep the things that don't fit neatly into a README. The half-formed ideas, the lessons learned at 2 AM, the architecture sketches drawn on napkins. Twenty-plus years of building software, and I've learned that the most valuable insights are the ones scribbled in the margins.
I'm a full-stack developer and systems architect who still believes in the craft. In clean abstractions, thoughtful APIs, and code that reads like prose. I also believe in writing things down — not in polished Medium posts, but in the raw, honest way you'd fill a field journal on an expedition.
Flip through. Grab a pencil. Leave a note in the margins if something resonates.
Currently working on
- Migrating legacy auth service to Node 22 + native fetch
- Setting up Dokploy for self-hosted deployments
- Building a CLI tool for managing DNS across multiple providers
- Writing up field notes on VPS architecture patterns
- Exploring AI-assisted code review workflows
Recent field notes
-
Feb 14The Unreasonable Effectiveness of Writing Things DownWhy I still carry a physical notebook to architecture meetings, and what it taught me about system design.
-
Feb 08SSH Keys, Git Identities, and the Multi-Org DeveloperLessons from managing a dozen GitHub organizations without losing my mind (or pushing to the wrong remote).
-
Jan 30Self-Hosting in 2026: A Field GuideMoving from Platform-as-a-Service to a single VPS. The costs, trade-offs, and unexpected freedom.
-
Jan 22On Naming Things (Again)A taxonomy of repository naming conventions that actually scales across organizations.
-
Jan 15The Monorepo Question Nobody AsksIt's not "monorepo vs. multirepo." It's "what kind of coupling are you willing to accept?"