Codewalkers
A publication about AI coding tools and agents, written by people who actually ship with them. I'm the lead author and editor there.
Codewalkers is where my practical writing lives: hands-on guides to coding agents, AI-assisted development workflows, and the tools themselves, tested against real projects before anything gets published. I'm the lead author and editor, which in practice means I write most of it, rewrite the rest, and kill anything that reads like it was generated. The editorial bar is simple: if a guide doesn't come from actually using the tool on real work, it doesn't run.
Guides from use, never from press releases
The AI tooling space is drowning in coverage written by people who spent twenty minutes with a tool and three hours with its marketing page. Every Codewalkers guide comes from running the tool against real codebases with real deadlines, long enough to find the sharp edges. Where a tool falls over, the guide says so, with the exact scenario that broke it, because the failure modes are usually the most useful part.
The editorial split with this site
Codewalkers and this blog deliberately don't overlap. Codewalkers gets the practical material: how to set up a tool, which settings matter, what a sane workflow looks like. This site gets the opinions, the stories, and the scars, like the year I lost to over-engineering, or what I think of agent-swarm productivity theater. When a topic has both a how and a why, the how goes to Codewalkers and the why lands here, and the two link to each other.
Writing about AI without sounding like it
An occupational hazard of covering AI tools is that your prose starts reading like their output. Codewalkers maintains explicit style rules against it: the tics, the filler constructions, the em-dash confetti, the phrases that scream language model. Everything published gets edited by a human who has read too much generated text to be fooled by it. It's a strange skill to have needed, and by now it's one of the things I'm proudest of about the publication.
Where it's heading
The site is mid-rebuild on a deliberately boring stack: static pages, minimal dependencies, fast everywhere, with the same security-first supply-chain rules I apply to product code. More agent deep-dives and workflow write-ups are queued, including companion guides to things I only tell stories about here. If you want the practical half of anything on this blog, codewalkers.com is where it will show up.