
Addendum: Getting Claude to Write Release Notes in Plain English
A follow-up to "Forcing Claude Code to Speak Human": what's broken in Claude's changelog voice, a rule block to stop it, and five before-and-after rewrites.

"A cornered agent goes squirrely. When you push an autonomous agent into an impossible architectural dilemma with no exit valve, it will contort your codebase to survive." One way I've come to think

"When autonomous agents write code, the volume of engineering exhaust—plans, reviews, task packets, and benchmarks—rapidly outgrows the shipping product itself. Keeping that exhaust from polluting the

Three applications, seventy minutes apart, identical echoes. Notes on the industrialization of synthetic hiring.

A few weeks ago, I wrote about forcing Claude Code to speak human. Last week, I wrote about ripping AI ceremony out of a codebase. This memo is the follow-up, because the problem is far wider and more

I was asked to do a design review of a portion of a system recently, and I opened a decision document proposing a dictionary called RELEASE_FINGERPRINTS. Every prompt file in the project was to have i

Gemini has developed a bit of a reputation in the multi-agent space. I recently heard someone refer to it as the "idiot in the room" when it comes to long-term agentic coding. That is both unfair and