Blog
Research notes and updates on AI coding agents, verification, and shipping code you can trust.
Follow us on Medium
Your AI QA Engineer Now Runs on Every Vercel Preview
IronBee opens the preview deployment nobody opens, uses your app the way a person would, and comes back on the pull request with the root cause. It runs inside CI too, with nothing deployed at all.…
Read on Medium
Nobody Writes a Test for the Bug They Did Not Think Of
Ask a model to write tests and it grades its own homework, on the questions it chose. Ask it to use the software and it has to meet an answer it did not write. A few weeks ago I ran a small…
Read on Medium
The Price of a Bug Is Set by Where You Catch It
The same one line defect costs twenty seconds at the keystroke and a week in production. Adding another gate does not change that number. Moving the check inward does. Pick a bug your team shipped…
Read on Medium
Some bugs do not exist until you run the code
Static analysis and AI review can only judge how a change looks. The bugs that cost the most do not exist until the code runs. Years before any of this, I build an observability product. The job is…
Read on Medium
I became the QA engineer for my own coding agent. Help!
Your coding agent writes in an hour what your team used to write in a sprint. The part that decides whether that code is any good did not speed up at all. I am a backend developer. For years I did…
Read on Medium
What a Verification Loop Adds to a Coding Agent: A First Look
This is the opening post in an ongoing series. We start with one model pair on one project, and the analysis will continue across more models and more datasets. We are sharing early on purpose, and…
Read on Medium
Introducing IronBee: The Verification and Intelligence Layer for AI Coding Agents
AI coding agents are fast. They generate features, fix bugs, refactor code, often in minutes. But there’s a problem nobody talks about: they almost never verify their own work. An agent can…
Read on Medium