Styleguides are dead! Long live Styleguide-Flows!
summary
Argues that a living styleguide-flow combines four artifacts — presets like ESLint/Prettier, a written rules doc, custom Ember template lint rules, and incremental migration tooling — into a cycle that prevents bike‑shedding and drifting patterns. Shows concrete lint rules that detect deprecated concat helper and x-input via AST visitors, adds them to the project, and uses the lint-to-the-future dashboard to ignore existing failures, stage fixes, and track counts dropping over time. Outcome: new rules block future regressions immediately while allowing phased refactoring with measurable progress.
AI-written summary · about
chapters (7)
- 0:00Introduction to style guides
- 4:39Problems with traditional style guides
- 10:40Documenting custom patterns
- 15:45Creating custom lint rules
- 21:29Handling legacy code refactoring
- 26:04Introducing Styleguide-Flows
- 28:56Benefits and conclusion
related talks
28mThe Night of the Living Style Guides
48mA practical guide to style guide driven development
34mThe Dream of Styleguide Driven Development
01h 05mStyleguide-Driven Development
45mYour Styleguide is an API
45mMaintainable Style Guides
23mWhat They Don't Tell You About Creating New Style Guides
38mStyleguide-Driven Development