{"id":"nr-b13c0572-ai-code-volume-makes-review-blast-radius-the-better-unit","slug":"ai-code-volume-makes-review-blast-radius-the-better-unit","title":"AI Code Volume Makes Review Blast Radius the Better Unit","observed_at":"2026-09-13T11:14:17.693Z","record_date":"2026-09-13","date_kind":"observed_at","novelty":"new","source_platform":"newsletter.pragmaticengineer.com","topics":["software-engineering"],"entities":["The Pragmatic Engineer"],"related_patterns":[],"source_url":"https://newsletter.pragmaticengineer.com/p/what-is-happening-with-code-reviews","source_urls":["https://newsletter.pragmaticengineer.com/p/what-is-happening-with-code-reviews"],"basket":{"id":"0a002c08-692d-4485-b9dc-0ffc04cebcca","revision":3,"review_ref":"b13c0572","cluster_id":"8529c5a9-1d5a-4a57-b159-322f9f7ab3c0","mention_count":1},"type":"post","description":"Gergely Orosz's analysis asks how engineering review must change when agents create more code than teams can inspect line by line.","why_it_matters":"Engineering teams should measure accepted changes, escaped defects, rollback cost, review latency, and reviewer load instead of code volume alone. The evidence is an informed industry analysis and reported leader experience, not a controlled study proving that one replacement process is superior. Watch for teams that publish repeatable review designs and show lower defects without hiding risk in automated graders.","verification_level":"source-inspected-local","signal_type":"field_note","schema_version":"newruntime-agent-readable-v0.2","stable_id":"post:ai-code-volume-makes-review-blast-radius-the-better-unit","retrieval_nugget":"Gergely Orosz's analysis asks how engineering review must change when agents create more code than teams can inspect line by line. Code review must shift from counting changed lines toward understanding the blast radius and evidence attached to a change. This matters now because code generation capacity can rise faster than reviewer capacity, making a familiar approval ritual the new","status":"published","visuals":[],"editorial_provenance":{"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:cbaad6c25d4bb056e3f1838201f901380b2d3187c490bb85aa84945db4aa7ec3","reviewed_at":"2026-09-13T11:14:17.693Z","source_evidence_count":1,"verified_claim_count":2,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":2,"implication_count":1,"watch_condition_count":1,"related_record_count":0},"analysis":{"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Code review must shift from counting changed lines toward understanding the blast radius and evidence attached to a change.","observed_facts":[{"text":"Orosz reports growing concern among engineering leaders about review volume as AI agents generate more code and more pull requests.","source_urls":["https://newsletter.pragmaticengineer.com/p/what-is-happening-with-code-reviews"]},{"text":"The article examines whether established pull-request review can absorb that change or needs different verification practices.","source_urls":["https://newsletter.pragmaticengineer.com/p/what-is-happening-with-code-reviews"]}],"mechanism":"The mechanism is risk-based review: classify affected systems, require targeted tests and traces, surface architectural consequences, and spend human attention where failure impact is highest.","why_now":"This matters now because code generation capacity can rise faster than reviewer capacity, making a familiar approval ritual the new delivery bottleneck.","implications":["Engineering teams should measure accepted changes, escaped defects, rollback cost, review latency, and reviewer load instead of code volume alone."],"evidence_boundary":"The evidence is an informed industry analysis and reported leader experience, not a controlled study proving that one replacement process is superior.","watch_conditions":["Watch for teams that publish repeatable review designs and show lower defects without hiding risk in automated graders."],"related_records":[],"new_branch_reason":"No existing New Runtime analytical record covers this exact management and technical mechanism closely enough."},"routes":{"html":"https://newruntime.com/posts/ai-code-volume-makes-review-blast-radius-the-better-unit/","markdown":"https://newruntime.com/posts/ai-code-volume-makes-review-blast-radius-the-better-unit.md","json":"https://newruntime.com/posts/ai-code-volume-makes-review-blast-radius-the-better-unit.json"},"editor":{"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]},"next_reads":[{"type":"topic","path":"/topics/software-engineering/","url":"https://newruntime.com/topics/software-engineering/","title":"Software Engineering","reason":"Explore the software-engineering topic hub.","media_type":"text/html","markdown_url":"https://newruntime.com/topics/software-engineering.md","json_url":"https://newruntime.com/topics/software-engineering.json"},{"type":"collection","path":"/posts/","url":"https://newruntime.com/posts/","title":"Field Notes","reason":"Open the latest editorial analysis.","media_type":"text/html","json_url":"https://newruntime.com/posts.json"},{"type":"collection","path":"/source-ledger.json","url":"https://newruntime.com/source-ledger.json","title":"Source Ledger","reason":"Inspect the public source evidence graph.","media_type":"application/json"}]}