Code Style and Violence
summary
Shows how concrete style rules and automation reduced a JavaScript repo from ~23,000 lint errors to ~3,000 using editorconfig, eslint with the Babel parser, Prettier, and stylelint; explains enforcement via husky + lint-staged hooks, protected branches and CI to block bad merges, and a custom npm commit-msg validator for Windows compatibility; reports that these measures cut frequent regressions to almost none over six months.
AI-written summary · about
chapters (15)
- 0:00Code style intro
- 3:20Popular code styles
- 6:18Setting up linters
- 9:07Git hooks for style
- 13:04CSS and React linters
- 15:55Fixing --no-verify issues
- 16:58Git Flow workflow
- 18:26Cross-platform hooks
- 21:46Branch protection with GitHub
- 24:20Code style results
- 25:28Linting error levels
- 27:30Common linting mistakes
- 28:53Branch protection rules
- 29:38Checks in CI pipeline
- 30:42Conclusion & Q&A
related talks
36mEnforcing coding standards in a JS library
16mClean code is no longer a myth
25mWrite Perfect Code with Standard and ESLint
13mMake linting great again!
31mDevelopment Standards: A Step-by-Step Guide to Implementing Them Without Pain
20mThey see me refactorin'. They hatin'
37mCoding Automation Lesson #1: Please Be Lazy
30mRefactoring large JavaScript codebases