Say goodbye to bugs and anti-patterns with Error Prone
summary
Picnic reports replacing repeated review comments by running Error Prone + Refaster as a compiler plugin and template refactoring layer, enabling automated fixes applied with patch mode applied in-place. The team builds an open-source toolkit with 750 refactor rules and 40 custom Error Prone checks, runs them across ~60 Java repos, and rewrites about 33,000 lines in staged commits; the rules land, reviewers accept them, and CI prevents regressions so the fixes stick.
AI-written summary · about
chapters (11)
- 0:00Introduction and frustration
- 5:50Automating code quality
- 10:24Setting up Error Prone
- 12:11Live demo of Error Prone
- 15:26Key bug patterns in Error Prone
- 19:18Gradual rollout strategy
- 23:57Error Prone at Picnic
- 26:25Picnic’s custom rules
- 31:59Validating rules at scale
- 35:30Encouraging contributions
- 37:43Conclusion and resources
related talks
48mSay goodbye to bugs and anti-patterns with Error Prone
01h 57mAutomatically improving Java codebases with Error Prone
45mAutomating away bugs with Error Prone in practice
49mStreamlining large-scale Java development using Error Prone
31mError Prone: Google's Secret Weapon for Bug-Free Lines of Code
43mCracking the Code Review: from Guesswork to Automated Guidance
21mCode reviewing like a champion
45mCracking the Code Review