Local DevOps Panel Discussion
summary
Panelists report concrete payoffs and concrete failures: embedding ops on dev teams embed ops with devs produces immediate empathy and fewer handoffs, while creating a named DevOps team stalls adoption — don't name a team DevOps. Automation runs in Jenkins, monitoring and SRE roles split responsibilities, and a move from ~50 to thousands of servers forces architectural rework. Micro‑team experiments from Apple-style DRIs teach more about coordination than deliverables, documentation hacks fail, and the winning moves are mentorship, mission statements, and executive backing.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:43Gwen Dobson
- 1:37Wes Novak
- 3:00Mike Davis Director of Software Engineering
- 5:27Define What Devops Is in the Organization
- 12:12Successful Strategies for that Cultural Shift
- 30:39Litmus Test for a Successful Devops Implementation
- 33:20Favorite Podcast
- 33:44How Do You Stay Educated and up-to-Date
- 36:32Who Can Define What Devops Is
related talks
46mPanel discussion "DevOps"
01h 02mWe have DevOps. No one was fired. But what to do?!
44mDevOps for developers (or maybe against them?!)
28mDevOPs Lessons for Frontend Developers
50mDevOps Project Failures - Lessons Learned and Strategies for Recovery
58mDevOps Counseling: 10 ways to help your Dev and Ops people love each other
39mPutting the Ops in DevOps
24mHow DevOps changed the way we operate software
