Software inspection
by Tom Gilb · first published 1993
3mentions
1recommended by
2HN commenters
2013–2015first – last mentioned
50% recommend50% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
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…
on “Ask HN: How can I run an effective code review?” ↗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".…
on “Ask HN: What should every software engineer know?” ↗…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…
on “Well Crafted Code, Quality, Speed and Budget” ↗