A Flip Is a Missing Rule
A colleague sent me the cleanest bug report I've had all year. He'd taken an open change, squashed it, and opened it again — same content, byte for byte, as…
A colleague sent me the cleanest bug report I've had all year. He'd taken an open change, squashed it, and opened it again — same content, byte for byte, as…
I had already published the warning: if a model only judges what a scanner shortlisted, a site the scanner fails to flag is a false negative nobody ever sees.
My reviewer caught a deleted flush call three times out of three, and said nothing about eight of thirteen removals in any run.
I had a harness measuring whether a set of skills helped a cheap model. It came back negative: no lift worth the tokens. I believed it.
I built an eval to tell me whether my agent's skills were earning their place. For a while it said they weren't — clean, green, confident.
Two reviewers, the same commit — a fat change, a few thousand lines. One was a deep reviewer I own, running a portfolio of judgment rules tested across a…
An AI reviewer finds three bugs on a real PR. Tell it to expect four or five and it finds more — but only more of what it could already see.
I spent a stretch trying to make an AI code reviewer cheaper without letting it miss more. Cost and recall, two dials pulling against each other.
Ask a code-review tool how good it is and you'll get a precision answer: of the things it flagged, how many were real.
In the Second World War, the Statistical Research Group was asked where to add armour on bombers, and handed the damage data from the planes that came back …
A fast eval told me a restructured module was clearly better. Comfortable margin. I ran it again to be sure, got the same verdict, promoted the new version…