- The Expensive Minute. 200 PRs a day was supposed to buy me leisure. Instead each minute got more expensive, and the idle ones cost the most. Keynes promised the fifteen-hour week; Linder explained why it never arrives.
- The Importance of Backpressure. Kanban cards were backpressure in physical form: a fixed number in circulation, so upstream could not outrun downstream. Software kept the board and dropped the pressure.
- One Hundred, and Fifty. I hit 100 merged PRs in a day this afternoon, not long after turning 50. Both are round numbers, and both are more useful as questions than as trophies.
- Build Your Own Lightsaber. Vibe code your own harness tools. Like building your own lightsaber, it teaches you how the thing actually works, and it should be cheap enough to throw away.
- More Attention, Not Less. I set a goal of 100 PRs a day because I was drowning in context switches. The target forced me to treat my own attention as the bottleneck.
- Anthropic's definition of safety is too narrow. Anthropic treats safety as a model behavior problem. Claude Code's recent month shows it's also reliability, pricing, and communication. They're where trust actually gets spent.
- People Systems Are the Next Codebase. An HR team vibe coded their own performance review tool. The interesting part isn't the tool -- it's what it means for how we treat people processes.
- Resisting AI. The skeptics say AI is another Kubernetes — a misapplied tech hype cycle. I think it looks more like the Internet, and probably much more.
- Make it impossible, or Make it safe. My dad's safety philosophy turns out to be a great framework for agentic coding: don't bubble-wrap the world, engineer one where you can take risks.
- Early observations from Interviews with Engineering Teams Adopting AI. The teams succeeding with AI aren't the ones with the best tooling. They're the ones that changed how they work.
- The first PRs shipped by Customer Success. Last week our customer success team shipped their first two pull requests. It changed how we ship and how we communicate.
- Battleship Prompts. Same task, three different prompts. See which one gets closest. It's surprisingly effective and makes you a better prompter.
- A Demographic Collapse of Developers. Junior developer hiring is stalling. Meanwhile, the senior pipeline doesn't refill itself.
- 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.
- Tool Augmented Prompting. Your linter, compiler, and test runner already talk to the AI. Make them say something useful.
- Do as I say not as I TODO. Your AI assistant holds a mirror up to your codebase. 5 ways to make sure it reflects the good parts.
- 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.
- Faster horses and AI Productivity. Not all AI productivity gains are real. A framework for telling the faster horses from the genuine improvements.
- The 'Comment-Only' Prompt. A new prompt I've found useful: Don't make any changes, just put a comment where you intend to make changes.
- 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.
- What is the 'why now' of your startup? What is the 'Why Now' of your startup?
- Will we become gut bacteria for AI? What is the role for humanity in a world of AI?
- Do you feel comfortable being flown by an AI pilot? Self-Flying. Will AI and Machine Learning replace your Captain and First Officer?
- What will self-driving cars do to cities? Once we have electric and self-driving cars, what happens to all the land blighted and consumed by roads?