One developer, around a dozen real projects, built in the open with AI doing a lot of the typing. This is where I write down what actually happened: the decisions, the mistakes, and the things that turned out to matter. No hype, no guru voice.
-
How I run 15 projects with Claude Code without losing the thread
The architecture of my order system: how work enters from emails, sessions and error reports, how Claude Code decides what runs unattended in a git worktree, and the cost caps and prompt injection checks that keep it from going wrong.
Read the full article -
Your CLAUDE.md is a briefing, not a boundary
Three parallel Claude Code sessions, one shared config file, no lock. One deleted an exception another had just added and took a production feature offline. The fix was not a better prompt, it was a hook that returns an error.
Read the full article -
A required field made my AI fabricate statistics
My content pipeline never researched a single number. A mandatory statistic field quietly forced the model to invent them, with real-sounding sources, in content people rely on. The fix was not a better prompt. It was deleting the field.
Read the full article
Everything else I have written →
Get new posts by email
One mail when a new post is out. Nothing else: no drip campaign, no tracking, no "quick question" follow-ups. Unsubscribe with one click, any time.
Double opt in: you get a confirmation mail first. Your address is used only to send these posts. Controller: Martin Schenk S.L. · Privacy