A Convincing Review of the Wrong Path
This article follows Executor Model, Reviewer Model: Why Cross-Vendor Code Review Actually Works , where I wrote about using a second model to validate review findings. This time, the missing check was not another opinion. It was running the code. I am the only user of my personal assistant app, so every issue in its tracker is one I filed after watching something fail on my phone. One was the fasting timer. I told it in chat that I had started a fast at seven in the evening, and nothing started. I handed that issue and eight others to Claude. It read the source, quoted the right files, and explained why the timer could not fail the way I described. I closed all nine issues that afternoon. A few days later I asked Claude to check again, but this time it had to run the reported inputs. Four verdicts flipped. The second pass took six and a half minutes instead of two and a half. Those extra four minutes recovered four real bugs and found two more I had never noticed to file. T...