But... you're not Facebook
summary
Claims that most front-end teams waste time chasing elite-scale optimizations and reinventing solved pieces: benchmarks from Facebook lead to blanket use of useCallback and heavy state stacks like Redux even though 99% of web devs don't work for Facebook; creator of Redux warns it’s often unnecessary. Built product examples include a developer-focused browser sold for a $5 subscription that previews multiple devices, simulates dark/light modes, and organizes local projects after two years of work. Concrete surprises: landing pages average under a minute of attention and startups often ship animations instead of features—stop solving non-existent problems.
AI-written summary · about
chapters (23)
- 0:00Introduction and setup
- 1:03Who works for Facebook?
- 2:08Meet the rectangle mover
- 4:15Pineapple on pizza analogy
- 5:17Stop solving non-existent problems
- 6:18Horsey and inline functions
- 7:00You're not Facebook
- 8:02Lighthouse and test coverage obsession
- 9:48Listen to your users
- 11:11The developer burnout cycle
- 12:35Over-engineering and ego
- 14:41Blogging vs building blogs
- 15:44Startup weekend lessons
- 17:09Solved problems: buttons
- 17:50Solved problems: state management
- 19:16Why Redux is outdated
- 21:45Solved problems: styling
- 24:52CSS and environmental guilt
- 27:39Why I care about over-engineering
- 28:42Terminal will not last forever
- 31:28Embrace innovation
- 32:50AI will replace us
- 35:40Q&A and summary
related talks
34mNew Adventures in Front-End, 2021 Edition
14mBuilding the New Facebook with React and Relay
58mAlways crashing in the same car (the state of front end web development in 2022)
22mGoing beyond Redux. Diversify frontend state management
32mMiss the forest for the trees: How frontend developers fail to be engineers
36mWe're gunna program like it's 1999
17mBuilding The New Facebook With React and Relay
45mFrontend Perfor