
AI isn't slop. It's just the generic average. And not you
My agent's PR description had 10 AI tells in 99 words. My version of the same PR had 0.
Notes on Kubernetes, containers and sandboxing: the root cause, the fix, and the upstream PR when there is one.

My agent's PR description had 10 AI tells in 99 words. My version of the same PR had 0.
For years the good stuff from my day job died in PR descriptions. Then Claude Code built me a blog on Wix Headless in one evening, and now every fix worth telling becomes a post.
Part 4. The containerd fix finally merged. It isn't the fix I wrote, and two maintainers are the reason.
gVisor shifts its stub memory by a random gap, but since 2023 one queue was not moved with it. When the gap is small, that queue can land on a thread's stack and the sandbox can hang for good. The fix was one line.
gVisor answers your app's system calls with its own kernel, the Sentry, written in Go and running in user space. I learned its map one review comment at a time, from the maintainer who kept correcting me.
A safety method from MIT, three replayed changes, 54 plans, two blind judges, and a headline I had to take back.
I built prismantis for one terminal, mine. Seven days later it had 60 stars, 10 forks and PRs from people I've never met, and two of them were testing each other's fixes for the same bug. This is that week, day by day.
A pod in Terminating is not dying, it is waiting.
prismantis is a Claude Code mod that redraws Claude's replies with colored tables, highlighted code and mermaid charts, and nudges Claude to actually draw them. I launched it on 2 Oct and update this page with every release.
One lost signal hangs pod deletion. The maintainer's smaller fix was the better one.
People share their victories. A month later mine got reverted, and that was the right call.
Writing the fix was easy. The review was where the engineering happened.
From an outage that lasted hours to a client-side timeout in containerd, through a merge, a revert and a second PR.
One shell function that runs any kubectl command on every cluster.
The cluster creator gets admin by default. Now you can take it back without a rebuild.
An unhandled AppArmor case, millions of log lines, and a CLA nobody at work could pick.