A case study in non-blocking continuous code reviews
summary
Case study of a 2012 novice team that abandons pull requests: they use Subversion with no branching, trunk commits gated by continuous integration and a deployment pipeline, add a Kanban to review column, and enforce every commit reviewed later by someone who did not author it. Tests, static analysis and peer testing catch bugs; unreviewed commits can reach production, shortening lead time, reducing WIP and context switches, and producing faster feedback—auditors are stunned by the quality.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker background
- 1:08Why non-blocking code reviews
- 2:53Purpose of code reviews
- 6:06What code reviews should not be
- 9:17Code reviews as a gate or choice
- 12:09Team culture and code reviews
- 13:53Starting non-blocking reviews in 2012
- 15:39Key ideas behind non-blocking reviews
- 17:44Continuous review process
- 19:30Releasable code without blocking reviews
- 21:57Quality vs functionality in code
- 23:00Transaction cost and batching work
- 26:08Benefits of reduced transaction cost
- 29:17Accelerated feedback and user value
- 31:05Trust and management theory
- 33:33Regulated industries and alternatives
- 34:37Conclusion and cultural fit
