Pyre, Lints, Codemods, Code Quality, and You
summary
A five-step practical plan: identify a measurable problem, run pyre and pystatistics to get counts, recruit stakeholders, automate fixes or teach teams, and lock progress with stricter checks. Tools shown: libCST for AST codemods, fixit to turn codemods into lints, and pyre features like 5,000 errors suppressed then driven down and pystrict to force annotations on new code. Example codemod removes redundant enum annotated assigns and ships as many small PRs.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 1:27Five steps to code quality
- 4:14Why use Python types
- 8:31Enabling type checkers
- 10:37Gathering metrics with Pyre
- 13:47Writing code mods with LibCST
- 19:11Protecting progress with lints
- 20:00Q&A session
related talks
33mBuilding Code Quality
18mBuilding a Culture of Code Quality
21mTeach Your Old Code New Tricks: Automating Code Quality in Large Projects
25mBest Practices for Writing Clean and Maintainable Codes
29mManaging the code quality of your project. Leave the past behind: Focus on new code.
26m(Professionally) Coding with Others
43mBuild in Quality
30mAutomating Code Quality