Make Linting Great Again
summary
Argues that linting becomes useful only when it targets the exact files being committed, not the whole repo, and shows a workflow using husky plus lint-staged to run linters and autofixers only on staged files, cutting slow CI failures and noisy output. Claims developers spend ~50% of time hunting bugs and cites a $312 billion yearly cost, demonstrates automatic reformatting with prettier so commits are fast, relevant, and self-correcting.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:29What the lint?!
- 0:44Why lint?
- 1:32How to lint?
- 5:40Automatically fix lint errors
- 5:56Automatically reformat your code
related talks
19mMake Linting Great Again
13mMake linting great again!
34mLint to the Rescue
33mRoad to Zero Lint Failures: Tackling Code Quality Challenges at Scale
16mClean code is no longer a myth
29mThe Joy of Linters: Good Engineering Practices & Productivity Boosters
30mLint Your Code Into the Future
24mRoad to Zero Lint Failures: Tackling Code Quality Challenges at Scale