A co-worker told me a few weeks ago to stop using Claude to review Claude. “Codex is a better reviewer,” he said. I didn’t buy it. A reviewer is just a model reading a diff—why would the brand matter? If anything I expected a second model to add noise: different conventions, more findings to argue down. He was right. It took me a while to work out why. The Setup I had a self-contained thing to build: a single-user outliner notes app on Cloudflare.

Last month I opened a pull request that contained zero lines of code. Five markdown files, a decision log, a fact-check appendix, and a roadmap that explicitly admits which three decisions could still be wrong. That’s it. If you’d asked me a year ago whether I’d ship a “PR” like that, I’d have laughed. Designs were something you scribbled in a notebook on the way to the keyboard. The work was the code.

A Thousand Versions I wrote about Claude Desktop’s enterprise configuration a couple days ago after unpacking v1.1617.0 — Bedrock routing, token budgets, credential helpers, sandbox controls. Undocumented, shipping in every copy. Claude Desktop is already at v1.2581.0. Almost a thousand version bumps. The app structure changed under my feet — v1.1617.0 had readable JavaScript inside the Electron asar. The current version compiles core logic into native Rust and Swift binaries, with application code split across 553 minified JS chunks and a 10MB Vite bundle.