What Can We Learn With JavaScript Fatigue?
summary
Claims that npm registry explodes with tens to hundreds of thousands of packages are backed by numbers: npm has 425,989 packages and an author-measured ~764 new packages per day and registry traffic up ~1000x in five years. Toolchain realities—Babel, TypeScript, Browserify/module bundlers, Mocha/Chai/Sinon, Karma—exist to solve cross-browser and iteration problems. Practical prescriptions: adopt TDD for every problem, prefer small incremental “do things that don’t scale” steps, focus on solving business problems not collecting tools.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 1:13What is JavaScript fatigue?
- 3:41Reality of software development
- 6:54Design vs coding in software
- 8:41Quotes on performance and TDD
- 13:21Decision fatigue and productivity
- 19:50JavaScript ecosystem growth
- 22:16How to deal with JavaScript fatigue
- 28:39Do things that don't scale
- 31:05Cathedral vs bazaar in software
- 33:56Are we really engineers?
- 36:28The power of curiosity and networking
- 37:53Closing and Q&A
related talks
19mWhat Can We Learn With JavaScript Fatigue
23mWhat Can We Learn With JavaScript Fatigue?
41mThe Future of JavaScript Package Management
19mNavigating JavaScript Userland- 41mThe Future of JavaScript Package Management
41mnpm and the Future of JavaScript
45mNext Gen Package Management
57mnpm and the Future of JavaScript