Miss the forest for the trees: How frontend developers fail to be engineers
summary
Claim: frontend teams trade long‑term engineering discipline for chasing frameworks, causing repeated rewrites (one legacy app is rewritten three times during migration) and costly migrations between jQuery, AngularJS, React, Redux, MobX and Next.js. Evidence: interest curves cross around 2018 and end up roughly 50/50 for React vs jQuery; frameworks call your code and often optimize developers not users. Advice: favor governance, documentation and the ability to reproduce core features (try reimplementing a tiny framework). Built: a “State of Health” survey to gather data about developer wellbeing.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:55Why we forget our original goals
- 4:19Frontend evolution and frameworks
- 9:43Progress in rendering techniques
- 11:30The problem of code soup
- 13:13Framework tribalism and blame games
- 16:43Clean code vs framework hype
- 18:31Governance and decision-making
- 21:39State management before frameworks
- 23:48Frameworks as permanent crutches
- 24:54Context and user outcomes matter
- 26:17Delivering value over code
- 28:44The real job: predictable systems
- 30:31Mastering the basics first
related talks
50mI Don’t Care About Your JavaScript Framework
46mFunctional Frontend. Practical survival guide for backend engineers.
34mState of Frontend
58mAlways crashing in the same car (the state of front end web development in 2022)
49mFrom Frameworks to Superframeworks
46mA Round Table on The State of Front-End: (Ember, Angular, React)
34mWe need to talk about the front web
01h 22mAnti-fragile frontend development