Interview with Kyle Simpson

on YouTube ↗12m

" summary

Frameworks often mask the bare metal of JavaScript so teams ship faster on the happy path but have no way to diagnose failures when behavior breaks; real work shows apps running Angular React and jQuery simultaneously and teams piling abstractions into brittle stacks. Advice is to master the layer you use and also understand the layer below, strip frameworks away as an app matures, and adopt ES6 features like destructuring to favor declarative, more maintainable code.

AI-written summary · about

" chapters (7)

1. 0:00Choosing frameworks and JS fundamentals
2. 1:06Abstraction dangers and happy path coding
3. 2:50Mastery and layers below
4. 4:16Breaking out of JS easy paths
5. 6:02Frameworks as prototypes not platforms
6. 7:51Avoiding framework cheerleading
7. 9:15ES6 as new ways of old things

" related talks

• 50mI Don’t Care About Your JavaScript FrameworkNéstor Salceda, Dani Latorre · Software Craftsmanship Barcelona 2017
• 27mDesigning Even Larger (JavaScript) ApplicationsMalte Ubl · JSConf Hawaiʻi 2020
• 01h 02mChoosing a JavaScript FrameworkRob Eisenberg · NDC Oslo 2016
• 47mJavaScript Frameworks: There Should Be Only OneSergey Averin · HighLoad++ 2015
• 11mKyle Simpson (Getify Solutions) interviewed at Fluent 2014Kyle Simpson · Fluent 2014
• 06mBrian Holt (reddit) interviewed at Fluent 2014Brian Holt · Fluent 2014
• 49mI'm good at JavaScript, I swear.Jose Aguinaga · jsDay 2017
• 21mTesting Javascript: Building JavaScript applications you won't hateMichael Timbs · Laracon AU 2019