< More on 100PR

In my post 100 PRs/day per engineer I muse on some of the changes I'm making to hit 100 "meaningful" Pull Requests in a day. It's a fairly arbitrary number and challenge, but it's a motivating one.

This follows some of my post as I track along with this goal.

Clear Your AI Mind
The Claude Dichotomy. AI is creating a genuine dichotomy: teams drowning in AI-supercharged chaos, others are thriving. The difference is in the approach to transformation.
Build tools to Prompt, Spin the Bottle Neck, Do as I say not as I TODO
Skills I'm ceding to AI, Don't Believe the Hype
No agents, no plan, ship it. Why I prefer single-prompt one-shotting with AI coding tools over multi-step agents, swarms, and planning modes.
Infinite Monkeys, Know Your Models
Faster horses and AI Productivity. Not all AI productivity gains are real. A framework for telling the faster horses from the genuine improvements.
Sharpening the Axe (Branch), A Daily AI Chat, Skilled Humans in the Loop, My Current AI Coding Workflow, Your Brain on GPS, The Mythical Machine-Month, The 'Comment-Only' Prompt
What does it take to build towards 100 PRs/day per engineer? My day, my tooling, and the system changes that make high-volume AI-assisted shipping possible.
The pace of AI tools