Evaluating Technology
summary
Argues for concrete evaluation rules: prefer features that fail well (CSS Shapes leaves readable text, service workers enhance first-load without breaking older browsers), question who benefits (users vs developers), inspect assumptions and fallbacks, and treat web components cautiously — components must include meaningful markup fallback or they become empty shells (Polymer shop showed <shop-app></shop-app> with all logic in a single script). Cites service workers, web components, CSS shapes, and historical examples like Apollo software and Margaret Hamilton.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:47Code
- 3:06Technology
- 4:54Design vs Technology
- 8:00Hardware vs Software
- 9:16The World Wide Web
- 11:00Grace Hopper
- 13:21Design Principles
- 14:26CSS Shapes
- 16:03Service Worker
- 20:37Browser Support
- 21:09Web Component Design
- 23:07Who Benefits
- 27:05Biases
- 30:51Technology is the Driving Force
related talks
31mA Style for Every Occasion
33mGet the core right and the resilient code will follow
01h 02mJS UX: Writing Code for Humans
51mThe Business Of Front-End Development
47mNo more excuses left - let's build great things
54mHot Topics Panel
47mHow To Build Future Proofed Applications
24mA Working Theory Of Components