Improving the Quality of JavaScript Code
summary
Shows how to fix real JavaScript mistakes: prefer use const/let not var, prefer === over ==, enable "use strict" to catch undeclared variables, copy objects with spread to obey open/closed and DRY, and favor a functional pipeline (filter/map/reduce) to lower cognitive load. Recommends tooling and CI: npm install, npm test, then ESLint plus Plato in CI, with an example Plato score moving from 65% to 93% to 100% after refactoring.
AI-written summary · about
chapters (9)
- 0:00Principles of quality code
- 2:21Avoiding design violations
- 8:04Questioning and code quality
- 12:34Specific JavaScript quirks
- 17:42Modernizing variable usage
- 26:22Functional programming style
- 34:03Empathy and abstraction
- 38:25Leveraging automation tools
- 45:29Complexity and refactoring
related talks
58mImproving Quality of JavaScript Code
49mJavaScript: The Fascinating Parts
01h 01mRediscovering JavaScript
56mThe Better Parts
30mRefactoring large JavaScript codebases
21mTesting Javascript: Building JavaScript applications you won't hate
30m"JavaScript, the Real Bad Parts"
46mInvisible performance. How fast is your JavaScript code?
