Reviewing code requires reading
Summary
The article argues that code review is about diffuse responsibility and learning the codebase, not just gating production by unread code. It uses Charity Majors' perspective to critique pushing unread code, and highlights bus factor and team ownership with a demo example.