--- title: Rigorous Yet Sustainable Human Reviews in the AI Era description: Artie Shevchenko, speaking at Craft Conference, argues that AI is increasing code review volume faster than humans can sustainably keep up, creating 'cognitive... canonical: https://daily.dev/posts/rigorous-yet-sustainable-human-reviews-in-the-ai-era-wzkmyrq2h twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Rigorous Yet Sustainable Human Reviews in the AI Era | daily.dev og:description: Artie Shevchenko, speaking at Craft Conference, argues that AI is increasing code review volume faster than humans can sustainably keep up, creating 'cognitive... og:url: https://daily.dev/posts/rigorous-yet-sustainable-human-reviews-in-the-ai-era-wzkmyrq2h og:image: https://api.daily.dev/og/posts/wzKmYrQ2h.png og:image:alt: Rigorous Yet Sustainable Human Reviews in the AI Era og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Rigorous Yet Sustainable Human Reviews in the AI Era **[InfoQ](https://daily.dev/sources/infoq)** · 4 min read · 0 upvotes · 0 comments ## Summary Artie Shevchenko, speaking at Craft Conference, argues that AI is increasing code review volume faster than humans can sustainably keep up, creating 'cognitive debt' that erodes shared understanding of a codebase. He proposes a coding-first, AI-second workflow where developers build a spike, feed it to AI for improvement suggestions, then review changes with deep context already in hand. He also suggests letting code owners skip peer review and rely on AI-only approval for their own PRs, but stresses this only works when most team members are code owners and teams stay small, otherwise the review bottleneck simply shifts to the few remaining owners. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why is reviewing AI-generated code more mentally exhausting than reviewing human-written code? AI-generated changes tend toward deceptive correctness, meaning they look plausible at first glance while hiding subtle flaws that take more mental effort to spot than issues in human-written code. Combined with the sheer volume of incoming AI-generated changes, this pushes reviewers past their personal fatigue threshold faster, after which review quality drops exponentially. _Teams weighing how to scale code review against rising AI output track these workflow debates on daily.dev._ ### Does letting code owners approve their own PRs with AI review actually reduce team review bottlenecks? Only if most engineers on the team are already code owners and the team is small. If most engineers are not owners, the few owners still spend nearly all their time reviewing AI-generated changes from non-owners, so letting owners fast-track their own PRs barely affects overall team velocity or owner fatigue. _Engineering leads rethinking code ownership policies under AI-driven review load can follow this reasoning on daily.dev._ ## Similar posts on daily.dev - [Agentic Code Review](https://daily.dev/posts/agentic-code-review-0ue8fcsa1) · Addy Osmani · 147 upvotes · 14 comments - [Code Reviews in the Age of AI](https://daily.dev/posts/code-reviews-in-the-age-of-ai-acvy63drb) · Earthly · 1 upvotes · 0 comments --- Tags: [#ai-coding](https://daily.dev/tags/ai-coding), [#code-review](https://daily.dev/tags/code-review), [#company-culture](https://daily.dev/tags/company-culture) [View this post on daily.dev](https://daily.dev/posts/rigorous-yet-sustainable-human-reviews-in-the-ai-era-wzkmyrq2h) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Rigorous Yet Sustainable Human Reviews in the AI Era","url":"https://daily.dev/posts/rigorous-yet-sustainable-human-reviews-in-the-ai-era-wzkmyrq2h","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/rigorous-yet-sustainable-human-reviews-in-the-ai-era-wzkmyrq2h"},"datePublished":"2026-09-03T12:10:19.698Z","dateModified":"2026-09-03T12:11:14.967Z","description":"Artie Shevchenko, speaking at Craft Conference, argues that AI is increasing code review volume faster than humans can sustainably keep up, creating 'cognitive...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/85982360b01643df483eabbed77049eb?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/85982360b01643df483eabbed77049eb?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"InfoQ","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"InfoQ","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/afc3bced3e1e4b188dd9127017a60e0c","url":"https://daily.dev/sources/infoq"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/rigorous-yet-sustainable-human-reviews-in-the-ai-era-wzkmyrq2h","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-coding,code-review,company-culture","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"InfoQ","item":"https://daily.dev/sources/infoq"},{"@type":"ListItem","position":3,"name":"Rigorous Yet Sustainable Human Reviews in the AI Era"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/rigorous-yet-sustainable-human-reviews-in-the-ai-era-wzkmyrq2h#faq","mainEntity":[{"@type":"Question","name":"Why is reviewing AI-generated code more mentally exhausting than reviewing human-written code?","acceptedAnswer":{"@type":"Answer","text":"AI-generated changes tend toward deceptive correctness, meaning they look plausible at first glance while hiding subtle flaws that take more mental effort to spot than issues in human-written code. Combined with the sheer volume of incoming AI-generated changes, this pushes reviewers past their personal fatigue threshold faster, after which review quality drops exponentially. Teams weighing how to scale code review against rising AI output track these workflow debates on daily.dev."}},{"@type":"Question","name":"Does letting code owners approve their own PRs with AI review actually reduce team review bottlenecks?","acceptedAnswer":{"@type":"Answer","text":"Only if most engineers on the team are already code owners and the team is small. If most engineers are not owners, the few owners still spend nearly all their time reviewing AI-generated changes from non-owners, so letting owners fast-track their own PRs barely affects overall team velocity or owner fatigue. Engineering leads rethinking code ownership policies under AI-driven review load can follow this reasoning on daily.dev."}}]} ```