Welcome to the Blog
After years of keeping my notes locked in Obsidian, I am finally opening the vault. Here is why I am writing, what to expect, and how this space works.
I have 690 clippings, 23 Maps of Content, and hundreds of daily notes sitting in an Obsidian vault.
For years, I've treated writing as a private exercise. A way to untangle a messy architecture problem, distill a book, or capture a passing insight before it evaporated. But a private vault is a closed loop. It clarifies thought, but it doesn't test it.
I built this blog to change that.
The Pipeline
This isn't a traditional CMS, and I don't intend to write traditional SEO-optimized tutorials.
Instead, I've built an automated pipeline using Claude Code and a custom agent skill (draft-blog-post). When I want to publish, I point the agent at a cluster of notes in my Obsidian vault. It reads them, synthesizes the core insight, respects my privacy gates, applies employer redactions, and spits out a ready-to-review Markdown draft right into this repository.
I review it, tweak the voice, and run make publish.
What to Expect
The goal is two to four posts a month. The content will be a direct reflection of what I am actively reading, building, or untangling at any given moment:
- Book Notes: Long-form reflections on technical books, drawn from my reading highlights and marginalia.
- Architectural Patterns: Synthesizing concepts like Modular Monoliths, Domain-Driven Design, and decoupling.
- Tooling & AI: How I am integrating agentic workflows and LLMs into daily development.
- Monthly Rollups: Quick digests of the most interesting articles, talks, and papers I consumed that month.
It will be pragmatic, specific, and hopefully useful.
Welcome. Let's see what survives the migration from the vault to the web.