For a long time the bar for publishing felt higher than it needed to be. Essays on Substack have their place. They’re deliberate and polished. But day-to-day engineering isn’t neat essays. It’s half-formed hypotheses, things tried in a terminal, and small architecture pivots that don’t deserve 2,000 words.
So this dev log is a scratchpad for the build journey. Raw notes on tools and architecture, what worked and what didn’t. The reasoning behind small decisions, written down before I forget it six months later. And a running record of what happens when AI pair programming goes from novelty to the way I ship every day.
Every post is a Markdown file committed to git, right next to the code. Easy to write, so I’ll actually write.