• 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.
• 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.
• 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.
• Vibe Coding Dev Tools. Invest in your AI dev tools, but vibe code them. They will be eventually be disposable.
• We're not vibe engineering. Vibe coding is the headline. Engineering a new SDLC is the actual work.
• Clear Your AI Mind. Your context window is not a diary, don't forget to /clear.
• Spin the Bottle Neck. The bottleneck in software has moved. Teams are still optimising for the old (wrong) one.
• Still choose boring technology. Dan McKinley's classic advice on "choosing boring technology" is even more true in the AI era.
• AI Prompts are Wishes. AI prompts are wishes. The more powerful the wish, the bigger the potential for the curse.
• Skills I'm ceding to AI. My shortlist of coding skills I'm genuinely comfortable handing to AI.
• Don't Believe the Hype. AI vibe coding tools aren't truly there yet. But early adopters can see they will be. Those aren't the same thing.
• Infinite Monkeys. AI coding tools need a high degree of parallelism to work. Without it, you're just watching a monkey type.
• Know Your Models. Software engineers routinely juggle multiple AI models. Other disciplines will be encountering this soon.
• Sharpening the Axe (Branch). Using an Axe branch when iterating on your AI coding workflow.
• Skilled Humans in the Loop. Human-in-the-loop only works if the human has (and retains) the skills to actually be in the loop.
• My Current AI Coding Workflow. A snapshot of how I'm working with AI coding tools right now (Feb 2026).
• Your Brain on GPS. What happens to our navigation skills when we rely on GPS? And what might happen to our coding skills with AI?
• The Mythical Machine-Month. We're moving into an era where a team of 5 engineers can outperform a team of 50.
• AI and abandonware. Can we have AI maintain abandoned npm packages?
• The pace of AI tools. The rate that AI coding tools are adding workflow features is wild.
• Will you see bots in your email? Bots in email? With a dash of JSON-LD your emails become semantic. And open up new innovations.
• Have you licensed your ruby gems? We're used to Ruby gems being permissive licenses, but that's not always the case. Using gemfresh you can see what licences are in your Gemfile.
• Are your ruby gems fresh? Gemfresh is a quick and easy tool to see which Ruby gems in your Gemfile are ready for an update.