After 18 months and ~1,500 code reviews at Disy, this post shares practical recommendations and retrospective observations. Key advice includes keeping reviews short and focused (under 400 LOC), separating refactorings from new features, replacing exhaustive checklists with short personal ones and automation tools like SonarQube, providing reviewers with written context, and establishing a code of conduct covering goals, appropriate behavior, and conflict resolution. The retrospective notes that reviews improved knowledge sharing, code quality, and team discussions, but highlights a recurring issue: reviews often happen too late in development to challenge design decisions.
Sort: