Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
One of the reasons for the DevOps movement is that all developers should carry pagers and be on call, right? Well, not quite. However, there is a common area of conflict between operations and development teams about site outages related to application-related issues that developers know how to debug and fix much faster than operations typically does. In this talk, I'll discuss some companies that have successfully implemented developers on call" policies and what that means. I'll also discuss the business value, why it matters, and how it helps create a collaborative culture of sharing. Help us caption & translate this video! http://amara.org/v/FGbm/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled "You Should Be On Call, too" features Joshua Timberman discussing the intersection of development and operations within the context of DevOps. The central theme revolves around the idea that developers should actively participate in on-call responsibilities, fostering collaboration between development and operations teams to enhance efficiency and accountability in handling application-related issues. Key points discussed in the video include: - **The Importance of On-Call Participation**: Emphasizing that both developers and operations teams should share responsibilities to address production issues efficiently. - **Collaboration Over Blame**: Highlighting that the move towards developers being on call is not about assigning blame but about fostering a collaborative environment where Developers assist Ops in maintaining applications. - **Challenges with Silos and Communication**: Sharing anecdotes about how siloed responsibilities lead to inefficiencies and misunderstandings, especially when handling system alerts and notifications. - **Case Studies from Industry Leaders**: Mentioning companies like Opscode, Heroku, and Etsy, which have successfully integrated developers into on-call rotations, illustrating the value this brings in terms of ownership and rapid problem-solving. - **Incorporation of Tools and Automation**: Discussing how effective monitoring systems and automation can lead to a better shared understanding of application performance and reduce alert fatigue. - **Outcome of Shared Devolutions**: Outlining benefits such as increased morale, better system reliability, and a culture of shared responsibility, which aligns with the DevOps ethos. In conclusion, Timberman highlights that enabling developers to be part of on-call duties not only helps in solving immediate issues but also cultivates a deeper understanding of the applications they create. This intersection of roles lowers the burden on operations teams and results in improved overall business performance, ultimately contributing to a more fulfilling working environment. The talk encourages organizations to adopt these strategies as a part of their DevOps practices, enhancing collaboration and operational efficiency.
Suggest modifications
Cancel
