Hello 👋
My talk is about automating away bugs with Error Prone in practice. This powerful tool detects and
automatically fixes bugs and anti-patterns in your Java codebases. The goal of my talk is to show how other teams and companies can start introducing it. Besides fixing bugs, this tool helps reducing the useless repeated discussions (
bikeshedding) that can happen during pull request reviews. No
repeated discussions about trivial things, like common coding guidelines, subtle bugs, or code style issues. With Error Prone we can automate and enforce these decisions over our codebase. Make sure to watch the talk and ask questions if you are interested! 😄