Thinking about Thinking (About People)
summary
Shows that removing signs in Dutch shared space experiments actually cut objective crashes but some towns reversed changes because residents felt less safe; cites an Amazon page where at 2s users can act (89% visually complete) though full load is 5s, and Twitter’s concrete metric time to first tweet that drove engineering choices; argues for user-impact alerts not CPU-only monitors with examples (Groupon drop was a sold‑out deal, a server CPU spike came from a Windows update); recommends expanding team boundaries to include designers and security.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:45Amsterdam
- 1:30Traffic Engineering
- 4:20Page Load Time
- 5:00Does Page Load Time Reflect the Experience
- 6:40Time to First Tweet
- 7:40Monitor What Really Matters
related talks
44mTrollies, veils and prisoners
57mMove Fast and Learn Things: Principles of Cognition, Teaming...
26mCommunication: What are you Thinking About?
43mHow to deal with the social side of computing life
26mStop Solving Problems
34mTaking Human Performance Seriously in Software
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
29mThink twice, code once