The evolution of farm to table and code to customer
summary
History maps from 90s handoffs to 2000s config automation and restauranteur brigade practices, arguing DevOps improves by borrowing concrete rituals: developer for a day rotations, formal apprenticeship program hiring to diversify the pipeline, pairing engineers with support to feel customer pain, and explicit inclusion of security and big data on the delivery loop. Expect actionable steps — cross-role rotations, blameless postmortems, family‑meal style demos, on‑call shadowing — that claim faster, more reliable delivery by fixing communication and ownership gaps.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 5:57DevOps history and context
- 10:50Restaurant industry deep dive
- 20:14Lessons from restaurants for DevOps
- 27:15Future of DevOps culture
- 28:17Key takeaways and call to action
- 30:26Q&A and volunteer talk
related talks
32mLooking Back At 13 Years Of DevOps
44mDevops - Almost 10 Years - What A Strange Long Trip It's Been (Keynote)
27mDevOps and Baking
35mDevOps. Evolution of the Species
38mDevOps transformation – the good, the bad and the ugly
26mThe Timeless way of DevOps
51mDay 1 Ask the Speaker
44mDevOps for developers (or maybe against them?!)