Accelerating the Dev Loop with DCM Lints at Betterment
summary
Betterment runs a 12‑person Flutter team that enforces linting via DCM lints plus custom rules imported into two YAML files (an “all rules” file that gets opt‑out editing in analysis_options). Concrete wins: auto‑fix argument ordering, a use_build_context_synchronously lint that prevents stale navigation, banning gesture_detector to fix missed tap targets, and strategies to remove bang operators (migration stalled only by a massive PR). Result: fewer runtime incidents, faster shipping, less manual QA.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:03Why lints matter
- 6:01Linting architecture
- 8:28What is DCM
- 9:54Useful lint case studies
- 10:15Arguments ordering lint
- 12:03Avoid sync build context
- 13:30Prevent conditional hooks misuse
- 15:18Banning unsafe widgets
- 17:46Recommended lints
- 18:06AI code and lints
- 20:15Demo: updating lints
- 22:27Eliminating bang operators
- 28:13Q&A
related talks
20mCode Quality Gates for Large-Scale Flutter Apps
31mExploring Static Code Analysis techniques in Flutter
30mLint Your Code Into the Future
19mMake Linting Great Again
35mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
20mClean Code Base: Harnessing the Power of Android Lint and Custom Rules
37mFirst Do No Harm
13mMake linting great again!