Cracking the Code Review: from Guesswork to Automated Guidance
summary
Claims that bugs cost $316B (2013) set the stakes and the talk delivers concrete fixes: use Error Prone (with Picnic rules) for automatic bug detection and fixes, run OpenRewrite for large-scale migrations to avoid churn, and adopt Google Java Format plus Spotless to eliminate formatting noise. Practical tactics include PR templates with checklists, self-review before requesting reviews, tagging specific reviewers, inline code coverage in diffs, and using suggestion commits to apply small fixes immediately.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 4:02Code review fundamentals and benefits
- 9:42Creating review-friendly pull requests
- 17:19Self-reviewing code before submission
- 23:25Effective feedback in code reviews
- 30:46Automating code quality checks
- 41:03Tool adoption and team collaboration
- 42:28Conclusion and key takeaways
related talks
38mCracking the Code Review: from Guesswork to Automated Guidance
45mCracking the Code Review
45mCracking the Code Review
41mCracking the Code Review from Guesswork to Automated Guidance
21mCode reviewing like a champion
01h 02mEffective Code Review
40mAssuring top-notch code quality in the Java Universe
44mEffective Code Review