The previous post covered the side project where muda's standard came from. The first pipeline muda ran on after that was an internal platform at work: an AWS CDK app with five Docker images, three ECS services, an AWS Batch compute environment and a small website. A dev
In September a dev deploy of one of my side projects took 29 minutes, and a deploy of a commit that changed nothing updated all 11 of its CloudFormation stacks and rebuilt both of its Docker images. The pipeline had been built the way I build most things now, one
I use more than one Claude subscription. Most of the reason is usage: when one account runs low on its limits, I want to keep working on another. Claude Code normally has one login, so moving to another account means signing out and signing back in through the browser each
I have written a lot of posts about individual pieces of how I work, like the terminal, the multi-repo workspaces, the coordination bus, and the harness that drives the model. What I never had was one place that put them together, so when someone asked how I actually work,
The last two posts here were about the skills in this plugin — one learns my writing voice from my published posts, the other revises a draft section by section. Neither can do anything without a way to reach Ghost: to read what I've already posted, create a draft,
Fixing a draft used to mean regenerating the whole post. When a section didn't sound right, the new version would correct it and overwrite three others that were already fine, so I kept a corrected copy open in the Ghost editor, regenerated, and pasted the good paragraphs back
Your writing voice is already on the page. Everything you've published is a record of how you actually write — consistent enough that a tool can learn it from your posts, even if you couldn't spell it out yourself. ghost-blog-mcp is the Claude Code plugin
A few days ago I wrote about what happens when you tell Claude a task is urgent — the agent silently introduces correctness bugs and self-reports as confident as ever. The closing section proposed a sharper question: if the bugs are framing-driven rather than caused by any real time
I've been working with Claude Code long enough that the laughably bad time estimates have become background noise. Claude thinks a 90-second task takes 30 minutes. I ask it to plan a sprint that I know we can do in a few days and it thinks it
One of the best parts about Claude Code is that the "code" in the name is misnomer. The fact is that it can be used for a wide variety of things. I wanted to use it to help with some woodworking projects. But part of the problem was