Posts by Tag: developer-productivity
all of the articles we have posted and linked so far under the tag: developer-productivity
One Worktree, One Issue, One Agent
I ran a four-week worktree experiment for five months. It didn't cut my context switching. It let several agents run at once, and every new worktree quietly lost its untracked config. The loop, the hook that fixes it, and why I went back to a plain clone.
The Guess Comes Before the Diff
Part 1 built the review machine that keeps agent-written code honest. But verification keeps the code safe — it doesn't keep me sharp. A Craft Conference talk named the hole in my pipeline, and the fix costs three minutes per PR.
The Expensive Part Is Remembering
A long agent session cost me $6.89, and the model wrote almost none of it. Two-thirds of the bill was the agent re-reading its own past — and the fix was architectural, not stylistic.
Pencils Down Is a Review Process, Not a Vibe
DHH declared 37signals pencils down at Rails World 2026. But agents writing your code is the easy part. The policy only works if you can answer: who reviews, against what bar, and what happens when the review fails? Here's the review machine I built to make pencils down survivable.
The Implicit Signals Your Cloud Agent Is Reading
The prompt is only one input. The cloud agent also reads your issue structure, your git hooks, your hook decisions, and your environment variables — most of it silently, and not always the way you'd expect.
GitHub Cloud Agents Work When You Build the Feedback Loop
After 3-4 days of bad PRs, I learned the hard part of using a GitHub Cloud Agent isn't the prompt — it's the environment, hooks, and validation layers that tell the agent whether it actually succeeded.