DjangoCon US 2017 - Preventing headaches with linters and automated checks by Flávio Junior While it’s very common to enforce PEP8 code style with tools like flake8, it’s rare for Django projects to use any other types of tools for automated checks. However, linters and automated checks are a good way to enforce code quality beyond code style. Human-based code reviews are great, but if an experienced programmer leaves the organization, all quality-related knowledge they have will be gone. One way to prevent this is to make developers consolidate their knowledge as custom check tools. Instead of repeating to every junior programmer how they should code, experienced developers should write tools to do that for them. Having this kind of “executable knowledge” is great to ensure long-lasting good practices in organizations. Thankfully, Python already has a number of extensible linters and check tools that can be used to consolidate knowledge. Also, Django has the System check framework, which can be used to write custom static validations to Django projects. In this talk, we’ll discuss existing linters and tools, what benefit they bring to Django projects, how to extend them and how to build custom ones. Combined with IDEs, pre-commit hooks, and CI tools, linters can validate code at programming time, commit time, or CI time, thereby ensuring good practices in all development workflow. This talk was presented at: https://2017.djangocon.us/talks/preventing-headaches-with-linters-and-automated-checks/ LINKS: Follow Flávio Junior 👇 On Twitter: https://twitter.com/flaviojuvenal Official homepage: https://www.vinta.com.br Follow DjangCon US 👇 https://twitter.com/djangocon Follow DEFNA 👇 https://twitter.com/defnado https://www.defna.org/