--- title: "Reviewing code requires reading" url: https://daily.dev/posts/reviewing-code-requires-reading-rd1aqvza7 source_url: https://hauleth.dev/post/review-requires-reading type: article source: "Beam Bloggers Webring" published: 2026-06-04T18:29:32.511Z updated: 2026-06-04T18:29:53.147Z tags: ["ai-coding", "code-review", "company-culture"] reading_time: 3 upvotes: 0 comments: 0 language: 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. # Reviewing code requires reading **[Beam Bloggers Webring](https://daily.dev/sources/beambloggers)** · 3 min read · 0 upvotes · 0 comments ## Summary A rebuttal to Charity Majors' suggestion that developers should feel comfortable shipping AI-generated code without reading it. The author argues that code review serves two critical purposes: diffusing responsibility across the team so no single person bears the burden of bugs or downtime, and spreading codebase knowledge to reduce bus factor. Skipping review to accommodate AI-generated code eliminates both benefits and externalizes knowledge to a third-party AI provider. The author's answer to 'what would it take to ship unread code?' is a written liability waiver from whoever demands it. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [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), [#company-culture](https://daily.dev/tags/company-culture) [View this post on daily.dev](https://daily.dev/posts/reviewing-code-requires-reading-rd1aqvza7)