Say goodbye to bugs and anti-patterns with Error Prone
summary
Error Prone runs as a compiler plugin during builds and can both flag and automatically apply fixes in patch mode, turning thousands of repetitive review comments into refactors. Picnic reports enabling over 500 built‑in checks, creating about 900 refaster rules and 40 custom bug checks, rolling configuration to 70+ repositories and 3 million Java lines via a shared parent, and landing ~60 PRs across 40 repos. Tooling (Refaster, Error Prone Support repo) proves scalable and reviewable, though some rewrites need iterative compilation.
AI-written summary · about
chapters (15)
- 0:00Introduction and motivation
- 1:05Code quality issues and repetitive discussions
- 5:59What is Error Prone
- 11:00Maven profiles setup
- 13:07Live demo of Error Prone
- 17:31Bug patterns and examples
- 20:08Roadmap for introducing Error Prone
- 23:18Applying first bug pattern in practice
- 26:06How Picnic uses Error Prone
- 30:00Error Prone Support and custom rules
- 34:16Applying rules at Picnic scale
- 37:06Current state and adoption
- 39:14Creating a custom Refaster rule
- 42:54Conclusion and resources
- 43:37Q&A session
related talks
38mSay 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
25mHow we automated code maintenance
40mAssuring top-notch code quality in the Java Universe