🏁 START HERE 🏁
Most of the guides I write didn’t exist when I needed them.
If you’re an engineer shipping AI into production, you’ll read these for the config files and the repos. If you’re a technical leader signing off on AI investments, you’ll read them for what actually works at scale (and what quietly fails). Either way, you get the version that skips the theory and starts with “here’s what I built, here’s what broke, and here’s the framework I extracted.”
These four posts are where most readers start. Pick the one closest to the problem you’re solving right now.
1. I Built My Own Observability for Claude Code 19,000+ readers found this on Google because nobody else had written it. A working Langfuse setup for tracing what AI coding tools actually do, with the repo you can clone today.
Start here if you build with Claude Code or Cursor and you’re tired of guessing what your agents did overnight.
2. The 3-Layer Claude Code Configuration That Runs 10 Projects The config architecture behind managing 17 AI projects without losing your mind. Global, project, and user layers, with every file shown.
Start here if you’re past the single-project stage and need AI tooling that scales across a team or portfolio.
3. I Built an AI Chief of Staff That Runs My Life While I Sleep 10 autonomous agents running overnight, unsupervised. The architecture, the failure modes, and the real decisions behind letting AI act instead of just answer.
Start here if you’re past the chatbot stage and want to see what production agentic systems actually look like.
4. Build Your Personal Wikipedia Andrej Karpathy described an LLM wiki architecture. I built an implementation you can install today. Two folders, one LLM, no RAG. The 3-step Compile-Query-Lint loop that turns scattered research into compiled knowledge.
Start here if you have research scattered across tools and want a structured knowledge base without the infrastructure overhead.
If one of those posts solves a problem you’re working on right now, the rest of the archive is more of the same: build something real, write the guide that didn’t exist, and extract the framework so you can apply it to your own work. One email per week, never more.
Subscribe free and every Build Log, Pattern Brief, and Framework Deep-Dive arrives in your inbox. Who I am, what to expect, and the paid tiers are all on the About page.