Wednesday 3rd April, 2013
5:00pm to 5:30pm
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.
I tweet about: Chef, Ruby, *ops, RPGs, video games, homebrew/craft beer, family, and politics. Internet meme and Buzzword compliant. I work for Opscode. bio from Twitter
Sign in to add slides, notes or videos to this session