Keynote – Kerri Miller
summary
Compares long-distance motorcycle rallies (1,000 miles in 24 hours; 11,000 miles over 11 days; 48 states in 10 days) to building ambitious software, arguing that complexity, subtle design bugs (the dwarves and cat vomit example) and emergent failures are inevitable and require plan B resiliency such as feature flags, tested reverts, and incremental launches. Uses LEDs vs incandescent traffic signals, the scientific method, maps vs territory, and Rails’ storytelling as concrete tools for deciding when to adopt or resist change.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:28Day Two
- 1:25Slack Channels
- 2:55Daily Schedule Slack Channel
- 7:10Reminders
- 9:55Carrie Miller
- 11:28Housekeeping Notes
- 11:47Keynote
- 22:32Traffic Signals
- 22:56Advantages to Leds
- 25:53Purpose of the Scientific Method
- 28:14Maps
- 36:17Adopt Best Practices
related talks
43mKeynote: A tech görl origin story
46mClosing Keynote
43mThursday Keynote -- What Programming is Really About
59mKeynote
01h 04mKeynote: Learn Programming, then Learn how to Be a Programmer
56mKeynote: Rethinking Computer Science Education
01h 00mKeynote
15mKeynote: Creating a Holistic Developer Experience
