--- title: AI broke code review. What about knowledge sharing? description: AI-generated code has made traditional line-by-line code review impractical, since engineers can't carefully read the volume of diffs produced. Beyond... canonical: https://daily.dev/posts/ai-broke-code-review-what-about-knowledge-sharing--hwpkhvgqt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: AI broke code review. What about knowledge sharing? | daily.dev og:description: AI-generated code has made traditional line-by-line code review impractical, since engineers can't carefully read the volume of diffs produced. Beyond... og:url: https://daily.dev/posts/ai-broke-code-review-what-about-knowledge-sharing--hwpkhvgqt og:image: https://api.daily.dev/og/posts/HwPKhVGqT.png og:image:alt: AI broke code review. What about knowledge sharing? 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. # AI broke code review. What about knowledge sharing? **[The New Stack](https://daily.dev/sources/newstack)** · 6 min read · 0 upvotes · 0 comments ## Summary AI-generated code has made traditional line-by-line code review impractical, since engineers can't carefully read the volume of diffs produced. Beyond bug-catching, review historically served a knowledge-sharing role, letting juniors learn from seniors and teams build shared mental models. Drawing on conversations with Vanitha Kumar (ThoughtWorks) and Margaret-Anne Storey, the piece introduces 'cognitive debt' - the erosion of shared understanding when AI writes code that nobody fully grasps. The proposed fix is 'intent-driven verification': capturing acceptance criteria, constraints, and architectural decisions before code is submitted, so reviewers evaluate intent rather than implementation. Aviator's Verify product is presented as a tool implementing this approach. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is cognitive debt in software engineering teams using AI-generated code? Cognitive debt is a term coined by researcher Margaret-Anne Storey describing what happens when a team stops understanding the system it is building because AI generates most of the code. Unlike technical debt, which lives in the code itself, cognitive debt lives in people: it builds up silently, has no dashboard to detect it, and shows up when teams can no longer explain why features exist or make changes confidently. _daily.dev surfaces practical takes on avoiding cognitive debt for teams scaling AI-assisted coding._ ### What is intent-driven verification in code review? Intent-driven verification is a code review approach where engineers capture the architectural decisions, tradeoffs, and scope calls made during a coding session with an AI agent, writing them as acceptance criteria before submitting the change. Reviewers then evaluate whether the right problem was solved with the right constraints, rather than reading every line of a diff, which Aviator's Verify tool is built to support. _Developers rethinking code review workflows around AI can track approaches like this on daily.dev._ ## Similar posts on daily.dev - [AI Code Review Best Practices](https://daily.dev/posts/ai-code-review-best-practices-ii7hbaa3j) · Aviator Blog · 15 upvotes · 1 comments - [How long before we stop reading the code?](https://daily.dev/posts/how-long-before-we-stop-reading-the-code--omchyubsd) · The New Stack · 1 upvotes · 0 comments - [Code Review Has Changed. The Contract Needs to Change Too.](https://daily.dev/posts/code-review-has-changed-the-contract-needs-to-change-too--9t5wi90oo) · Kilo Blog · 1 upvotes · 0 comments --- Tags: [#ai-coding](https://daily.dev/tags/ai-coding), [#code-review](https://daily.dev/tags/code-review), [#technical-debt](https://daily.dev/tags/technical-debt) [View this post on daily.dev](https://daily.dev/posts/ai-broke-code-review-what-about-knowledge-sharing--hwpkhvgqt) ```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":"AI broke code review. What about knowledge sharing?","url":"https://daily.dev/posts/ai-broke-code-review-what-about-knowledge-sharing--hwpkhvgqt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/ai-broke-code-review-what-about-knowledge-sharing--hwpkhvgqt"},"datePublished":"2026-08-19T17:04:48.754Z","dateModified":"2026-08-20T11:29:42.811Z","description":"AI-generated code has made traditional line-by-line code review impractical, since engineers can't carefully read the volume of diffs produced. Beyond...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5b8df3d70b0124831b23c8b33c3108e5?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5b8df3d70b0124831b23c8b33c3108e5?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"The New Stack","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":"The New Stack","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/newstack","url":"https://daily.dev/sources/newstack"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/ai-broke-code-review-what-about-knowledge-sharing--hwpkhvgqt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-coding,code-review,technical-debt","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"The New Stack","item":"https://daily.dev/sources/newstack"},{"@type":"ListItem","position":3,"name":"AI broke code review. What about knowledge sharing?"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/ai-broke-code-review-what-about-knowledge-sharing--hwpkhvgqt#faq","mainEntity":[{"@type":"Question","name":"What is cognitive debt in software engineering teams using AI-generated code?","acceptedAnswer":{"@type":"Answer","text":"Cognitive debt is a term coined by researcher Margaret-Anne Storey describing what happens when a team stops understanding the system it is building because AI generates most of the code. Unlike technical debt, which lives in the code itself, cognitive debt lives in people: it builds up silently, has no dashboard to detect it, and shows up when teams can no longer explain why features exist or make changes confidently. daily.dev surfaces practical takes on avoiding cognitive debt for teams scaling AI-assisted coding."}},{"@type":"Question","name":"What is intent-driven verification in code review?","acceptedAnswer":{"@type":"Answer","text":"Intent-driven verification is a code review approach where engineers capture the architectural decisions, tradeoffs, and scope calls made during a coding session with an AI agent, writing them as acceptance criteria before submitting the change. Reviewers then evaluate whether the right problem was solved with the right constraints, rather than reading every line of a diff, which Aviator's Verify tool is built to support. Developers rethinking code review workflows around AI can track approaches like this on daily.dev."}}]} ```