~/talk

A case study in non-blocking continuous code reviews

slides:none on file

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

  1. 0:00Introduction and speaker background
  2. 1:08Why non-blocking code reviews
  3. 2:53Purpose of code reviews
  4. 6:06What code reviews should not be
  5. 9:17Code reviews as a gate or choice
  6. 12:09Team culture and code reviews
  7. 13:53Starting non-blocking reviews in 2012
  8. 15:39Key ideas behind non-blocking reviews
  9. 17:44Continuous review process
  10. 19:30Releasable code without blocking reviews
  11. 21:57Quality vs functionality in code
  12. 23:00Transaction cost and batching work
  13. 26:08Benefits of reduced transaction cost
  14. 29:17Accelerated feedback and user value
  15. 31:05Trust and management theory
  16. 33:33Regulated industries and alternatives
  17. 34:37Conclusion and cultural fit
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.