Development Standards: A Step-by-Step Guide to Implementing Them Without Pain
summary
Explains how to implement automated, enforced development standards by storing rules in the repo and running linters both in editors and in the build pipeline. Names specific tools: EditorConfig, HTMLHint, stylelint, stylefmt, CSSComb, ESLint and Prettier, and describes using git hooks (husky) and CI to block invalid code; recommends starting from shared ESLint configs rather than configuring all ~250 rules yourself.
AI-written summary · about
chapters (14)
- 0:00Development standards intro
- 1:10Guidelines vs code style
- 4:43Unified code style benefits
- 7:11Linter success conditions
- 7:54EditorConfig setup
- 10:01HTMLHint for HTML
- 12:06Stylelint for CSS
- 16:27ESLint for JavaScript
- 21:48Code formatting tools
- 22:51Git hooks for bad code
- 24:37Git Flow branch management
- 25:38Strict rules fixes
- 27:45CI protection for repo
- 29:08Final standards checklist
related talks
25mWrite Perfect Code with Standard and ESLint
47mDevelopment Best Practices: An Overview of Working in the Software World
31mCode Style and Violence
17mHow to Ensure Code Quality and Consistency in Distributed Teams
36mEnforcing coding standards in a JS library
01h 01mUseful Tools and Utils for JS Development
37mCoding Automation Lesson #1: Please Be Lazy
26m(Professionally) Coding with Others