Replace the Trivial, Augment the Difficult
A rule in the code-review engine I built caught an idiom I've been writing for years and can no longer see. That's the small half.
A rule in the code-review engine I built caught an idiom I've been writing for years and can no longer see. That's the small half.
A change lands in review with everything green. The rules pass, the types check, the tests are close to the ones I'd have asked for.
The request was: let me arrange these panes how I like, give the arrangement a name, and hand it back to me tomorrow on a different laptop.
One evening an agent working in this repo killed an idea of mine for failing a rule. The kill was well argued and it cited the rule by line number, the way…
It looks at a deprecation deadline declared in a schema, calls new Date(), compares, and if the deadline has passed it fails.
My reviewer caught a deleted flush call three times out of three, and said nothing about eight of thirteen removals in any run.
A newer engineer left a note on my pull request: this array should be readonly. He was right.
Sixteen minutes and sixteen dollars to surface four low-severity nits, most of it spent scanning for rules rather than judging code.
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.
The reflex, when a model meets something long, is to make it shorter. Summarise the PR, TL;DR the paper, have the agent review the diff and hand back the…
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.
The goal was never a cheaper reviewer. It was finding everything that is really there while posting nothing that isn't — and that objective, not the budget…
A while back, I stopped reading the AI's end-of-task summaries and started watching the diffs. They came through faster than I could have typed them.
A description is a compression, and it drops the omissions it doesn't know it made — the case not handled, the check not added.
Linus Torvalds vibe-coded the visualizer and hand-wrote the audio math. One repository, the whole argument — writing code was never the scarce skill.