---
id: 20261017-T0-12
title: "代码审查该问的不是'有人看过吗'，而是'哪里可能出错'"
title_en: "Code Review Should Ask 'What Could Go Wrong,' Not 'Did a Human Read It'"
url: https://ai.daily.yangsir.net/daily/20261017-T0-12
issue_date: 2026-10-17
publish_date: 2026-10-16T22:06:37.000Z
category: insight
source_name: "Simon Willison"
source_url: https://simonwillison.net/2026/Oct/16/code-review/
---

# 代码审查该问的不是'有人看过吗'，而是'哪里可能出错'

Addy Osmani、Morgan Westlee Lunt和Qing Wang提出，用'有没有人读过代码'来判断代码审查质量是不准确的代理指标，真正该问的是'这次改动可能出什么问题，哪种检查——自动或人工——最适合捕捉它'。这一视角改变了审查发生的时机：过去审查是提交代码后的最后一道关卡，现在应更早介入，根据风险类型匹配对应的检查手段。

## English Version

**Code Review Should Ask 'What Could Go Wrong,' Not 'Did a Human Read It'**

Addy Osmani, Morgan Westlee Lunt, and Qing Wang argue that asking 'did a human read the code' is an imprecise proxy for code review quality. The better question: what could go wrong with this change, and which check—automated or human—is best suited to catch it? This reframing shifts when review happens. Previously a gate at the end of the workflow after writing code and opening a PR, review should now occur earlier and match checks to specific risk types.

---

**来源**：[Simon Willison](https://simonwillison.net/2026/Oct/16/code-review/)

**详情页**：https://ai.daily.yangsir.net/daily/20261017-T0-12

---

*智语观潮 · Daily — https://ai.daily.yangsir.net/llms.txt*