理解原理与方法：读 Tom Gilb 的《Software Inspection》。在实践中学习：读 Watts S. Humphrey 的《A Discipline for Software Engineering》。直接跳到后面的练习题就行，因为 95% 的价值都在练习题里，正文写得其实不怎么样……
How and why: Read "Software Inspection" by Tom Gilb Learn by doing: Read "A Discipline for Software Engineering" by Watts S. Humphrey. Skip to the exercises at the back, as 95% of the value is in the exercises, the main book is not that good…
质量控制方面的创新：需求评审、测试驱动开发（TDD）、Agile。建议读一读 Tom Gilb 的《Software Inspection》。《A Discipline for Software Engineering》后面的练习题也非常棒（尽管正文写得一般）。更新：理解“每小时清除的 bug 数”（bugs removed per hour）这个概念很有价值……
Quality control innovations: Requirements reviews, Test driven development, Agile. Have a read of Software Inspection by Tom Gilb. The exercises at the back of A Discipline for Software Engineering are also very good (although the main book is not that good). Edit: It is worth understanding "bugs removed per hour".…
…shows there's indeed plenty of agreement even without the science part. The minimizing f_n reflects well what the science established. Far as defects, problems people report are definitely a start. Fagan Software Inspection Process had the nice idea of standardizing in a list the kind of issues in code that would be treated as defects and fixed by priority. They could be lack of a bounds check, code style issue, whatever…
理解原理与方法：读 Tom Gilb 的《Software Inspection》。在实践中学习：读 Watts S. Humphrey 的《A Discipline for Software Engineering》。直接跳到后面的练习题就行，因为 95% 的价值都在练习题里，正文写得其实不怎么样……
How and why: Read "Software Inspection" by Tom Gilb Learn by doing: Read "A Discipline for Software Engineering" by Watts S. Humphrey. Skip to the exercises at the back, as 95% of the value is in the exercises, the main book is not that good…
质量控制方面的创新：需求评审、测试驱动开发（TDD）、Agile。建议读一读 Tom Gilb 的《Software Inspection》。《A Discipline for Software Engineering》后面的练习题也非常棒（尽管正文写得一般）。更新：理解“每小时清除的 bug 数”（bugs removed per hour）这个概念很有价值……
Quality control innovations: Requirements reviews, Test driven development, Agile. Have a read of Software Inspection by Tom Gilb. The exercises at the back of A Discipline for Software Engineering are also very good (although the main book is not that good). Edit: It is worth understanding "bugs removed per hour".…
……这表明即便没有科学论证的部分，大家确实也有很多共识。对 f_n 的最小化很好地反映了科学所确立的结论。至于缺陷（defects），人们报告的问题无疑是一个开端。Fagan 软件审查流程（Fagan Software Inspection Process）有一个很棒的想法，就是把代码中被视为缺陷、需要按优先级修复的问题类型规范化成一个清单。它们可能是缺少边界检查、代码风格问题等等……
…shows there's indeed plenty of agreement even without the science part. The minimizing f_n reflects well what the science established. Far as defects, problems people report are definitely a start. Fagan Software Inspection Process had the nice idea of standardizing in a list the kind of issues in code that would be treated as defects and fixed by priority. They could be lack of a bounds check, code style issue, whatever…