What Can We Learn With JavaScript Fatigue?

on YouTube ↗23m

" summary

Argues JavaScript fatigue often equals decision fatigue and backs it with numbers and histories: NPM 520k packages, npm traffic up 1,000×, and concrete tool chains like Babel, Webpack, Mocha, React, Node and mocha/Chai examples. Shows surprising error splits — 36% coding errors 64% design errors, NASA Apollo 73% design — and demos the practical rule set: take small steps, learn fundamentals on demand, build simple versions, avoid premature optimization, prefer single‑purpose tools and measure whether added complexity actually solves a real problem.

AI-written summary · about

" chapters (9)

1. 0:00Intro
2. 1:16Technology is not a go
3. 3:07Importance of good design
4. 8:46Why do we need these technologies
5. 14:02Dont be defined by your stack
6. 15:36Dig deep
7. 17:00Build things yourself
8. 18:22Microservices analogy
9. 19:30Conclusion

" related talks

• 19mWhat Can We Learn With JavaScript FatigueLucas Fernandes Da Costa · DevFest Nantes 2018
• 39mWhat Can We Learn With JavaScript Fatigue?Lucas Fernandes Da Costa · THE CONF 2017
• 23mWorse is Better: The Upside of JavaScript FatigueKevin Lacker · ReactEurope 2017
• 35mFighting the Front-end FatigueBenedek Gagyi · JSHeroes 2017
• 41mThe Future of JavaScript Package ManagementDarcy Clarke · OpenJS World @ Open Source Summit Europe 2023
• 58mImproving the Quality of JavaScript CodeVenkat Subramaniam · Great International Developer Summit 2023
• 20mJavaScript’s “+” Operator and Decision FatigueEmily Freeman · JS Kongress 2017
• 06mLightning talk from Andrey SitnikAndrey Sitnik · ReactiveConf 2017