Improving Quality of JavaScript Code
summary
Claims that long functions kill agility backed by an example of a 7000-line function and a concrete refactor path: rewrite imperative loops into functional pipelines, shorten functions, prefer const/let over var and use ===. Code samples (imperative, functional, concise) are linted with ESLint and measured with Plato; scores move from 64 to 93 to 100 maintainability and the CI step runs npm install then eslint and fails the build on errors, so the tools and metrics actually work.
AI-written summary · about
chapters (13)
- 0:00The importance of quality
- 2:36Why code quality matters
- 5:53Design and long functions
- 10:06Dangers of long functions
- 13:21The DRY principle
- 14:49JavaScript pitfalls
- 18:47Scoping and global variables
- 22:47Writing predictable code
- 27:28Functional programming
- 35:37Readable code patterns
- 39:53Maintaining code standards
- 43:51Tooling for code quality
- 55:11Closing and Q&A
related talks
58mImproving the Quality of JavaScript Code
40mRefactoring large JavaScript codebases
30mRefactoring large JavaScript codebases
45mConquering complexity: refactoring JavaScript projects
01h 01mRediscovering JavaScript
45mA Skeptics guide to functional style javascript
01h 03mFunctional Programming in JavaScript
49mJavaScript: The Fascinating Parts