About 90% of the code is written and reviewed by Claude. That one-sentence summary from Addy Osmani captures how the Claude Code team at Anthropic works. We believe these practices matter more than “how fast AI can write code”: once machines produce most of the output, the bottleneck shifts to whether the results can be trusted.
What this is
The Claude Code team has moved people away from reading code diffs line by line and toward defining “what counts as done,” then checking reproducible evidence. Before submission, Claude must launch the application and run it through its workflow; if it fails, Claude fixes the problem itself, and only escalates to a human after three consecutive failed attempts. The team has also compiled an incident checklist containing 39 rules, checking only the risks relevant to the current change each time.
The key design choice is to keep review rules somewhere the code changes cannot reach, preventing the AI from conveniently modifying the criteria used to judge its own work. Any issue missed by a reviewer is then turned into a new rule and used in backtesting. Claude Code now includes /verify; as of v2.1.286, it can enforce the project’s verification workflow before submission.
Industry view
Optimists argue that trustworthy verification allows people to manage dozens or even hundreds of AI coding tasks simultaneously. Boris Cherny estimates that giving Claude a clear verification method can make the final result two to three times better, but that is only his personal estimate. The claim that “task success rates can improve by as much as 10 percentage points” comes from Managed Agents’ internal testing of structured document generation, not from data produced by the Claude Code team.
The risks are just as clear: without testing data, “verification first” cannot be equated directly with improved reliability. AI-generated tests, benchmarks, and specifications can also enable machines to confirm themselves against faulty standards. End-to-end tests offer a more realistic picture, but they are slower and more expensive to maintain. When tests are flaky, AI may repeatedly rerun them and hope for a pass instead of fixing the root cause. Verifiers therefore need to remain independent of the code being tested and should be continuously checked against historical incidents.
Impact on regular people
For enterprise IT: AI coding tools are turning from code generators into engineering execution systems. Procurement priorities will gradually shift toward execution logs, audit rules, and mechanisms for human intervention.
For individual careers: Developers’ value will increasingly center on defining business rules, designing acceptance criteria, and judging anomalous evidence. Professionals whose role is limited to prompting models to generate code will continue to see their career space narrow.
For the consumer market: Software may be delivered faster, but consumers will not directly perceive how much AI was used. They will simply encounter products sooner that vary in feature completeness and receive updates more frequently.