Latest insights on product thinking, engineering excellence, and building software that ships faster and safer.
When AI generates code that breaks production, ownership doesn't transfer to the model — the post-mortem still names the human who clicked merge. Vibe engineering is the craftsmanship answer: you delegate the typing, but never the understanding, the design intent, or the accountability.
AI coding agents are multipliers. Multiply zero, get zero. Multiply a typical outsourced codebase, and you don't accelerate delivery — you accelerate rework. Here's the founder math on why your AI ROI is landing on the wrong substrate.
Most teams say they "do CI/CD" because they have a pipeline that builds, tests, and deploys. That pipeline is automation — Continuous Delivery is a discipline. Here are the practices that turn one into the other.
Most teams have heard of mutation testing. The reason 90% of them never run it: nobody told them how. This is the operating manual — pick the tool, read the report, kill the surviving mutants, run it fast enough to gate every pull request.
Even a good hypothesis needs a map before it needs code. AI agents build whatever ticket lands in front of them — they can't see the journey the ticket sits inside. User story mapping is the practice that turns a backlog of features into a walking skeleton of the user's journey. It's the second unlock.
Engineering resistance to AI tools is not a change management problem. Every complaint maps to a specific missing prerequisite. Here is how to read the resistance as a diagnostic — and the five-stage sequence that resolves it.
Median time from PR opened to first review is 22 hours. That is not review effort — it is system latency. Here is what it costs, why it happens, and what elite teams do differently.
Most founders evaluate engineering vendors on story points and velocity. Neither metric predicts whether software reaches customers. Here are the four questions — no technical background required — that reveal everything.
Every team with a legacy codebase hits the same wall: you cannot add tests without refactoring, and you cannot refactor without tests. Characterisation tests are the specific tool — invented by Michael Feathers, amplified by AI — that breaks the loop.