Automating the Wrong Things…
summary
Claim: teams automate the wrong parts and then watch maintainers undo savings. Concrete examples: run webpage test.org to get video timings and a checklist, stop sending retina images to everyone, and measure that the HTTP archive median page is 2.4 MB so bytes matter. Built things: forked Visual Studio Code to add autocomplete and merged it; use service workers and PWAs to make sites offline and installable. Surprising metric: >3s load loses roughly half users; fix assets first, then automate.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:14Web as universal platform
- 7:34Stop thinking about browsers
- 11:27Building for next billion
- 17:20Optimizing with modern tools
- 23:19Contributing to browsers
- 29:19Mobile web’s past mistakes
- 37:27Overcomplicating web dev
- 41:15Making web inviting
- 47:10Teaching web dev
- 50:23Progressive web apps
- 52:54Q&A
related talks
36m5 Ways to Boost Automation Effectiveness
53mAutomation Automation Automation
35mHow to Make Your Automation a Better Team Player
24mAutomating Access to Development
22mLess tech, more value tacking digital waste with sustainble produ
25mHow to do good without doing anything
51mRedefining test automation
53mScripting and Automation: This Manual Task Could Have Been a Script