Claude writes, a second model attacks: firmware output about 2x, fewer bugs
Half their effort goes to automated adversarial review. Claude plans and writes the code, Sol tears into it with only the coding standards to go on, and it costs about $300 per developer a month.
Done withClaudeSpotted· by HN user K0balt· Oct 15, 2026
Result Fewer bugs and clearer documentation
“We use a Claude for planning and generation, sol for adversarial review. Our metrics say we are about 2x.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
Runs a strict harness: specify everything in advance, plan, review the plan against the spec, implement and test, then a series of reviews by a different model with no context except the coding standards (test coverage, guidelines, smells, architecture). Roughly 10 percent of the effort is code generation, 40 percent documentation, planning and adversarial review, and 50 percent automated adversarial code review. Claude plans and generates; Sol does the adversarial review.
How it went
Their metrics say they’re about 2x as productive, at about $300 per developer per month, while shipping fewer bugs and clearer documentation. They credit the constant review by a different model, plus careful hand-offs between sessions.
Try it yourself with Claude
You're an adversarial code reviewer with no context except our coding standards: [paste standards]. Review this change: [diff]. Check test coverage, standards compliance, code smells, architecture and module boundaries, and anything that could break elsewhere. List each problem with its severity and a concrete fix. Don't praise anything.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
After $45 in GitHub Actions overage in one month, a solo founder put an idle homelab to work as CI runners, with Claude making it easy to set up. Daily spend dropped from $2-4 a day to under $0.25.
A first homemade synth has 36 hall-effect keys and buttons and 7 rotary encoders. The firmware started by hand, then gentle prodding at Claude got everything needed much faster. Rev 2 of the PCB is nearly done.
Working on a Quake project, Claude decided on its own to build a test suite: demo playbacks with snapshots compared pixel by pixel, plus recorded demos whose screenshots it checked for each element.
After building a minimal proof assistant, the writer asked Claude how they knew the prover was actually sound. Claude checked, found five different ways it could prove false theorems, and fixed them.
Four years after shelving a homemade RSS reader and selling off its $500 domain, the writer built it this year with Codex and Claude. They use it daily, along with 30 other strangers who found it public.
Chasing a childhood itch for the exact 1996 After Dark Flying Toasters screensaver, the writer turned to Claude. It did a lot of good reverse-engineering work, but kept inventing details that needed pushback.