First, I highly recommend "Deployment is just a part of dev/ops cooperation" http://www.kitchensoap.com/2009/12/12/devops-cooperation-doesnt-just-happen-with-de

First, I highly recommend "Deployment is just a part of dev/ops cooperation" http://www.kitchensoap.com/2009/12/12/devops-cooperation-doesnt-just-happen-with-deployment/ http://www.kitchensoap.com/2009/12/12/devops-cooperation-doe... Second, this isn't a question unique to the dev/ops relationship. What about the dev v. project manager? If you have a good team of developers, why have a PM? Having worked as a dev, a system engineer, and newly in the PM department, everything I've done since being a 'code monkey' is motivated by a desire to make the dev's jobs easier. Maybe that's because of my roots, but I think it makes the most sense. Where I work, we have a useful distinction between Sysadmins and System Engineers. Broadly speaking, admins are the i-dotters and t-crossers and do things with well-defined processes while engineers are responsible for everything else. As an engineer, I wanted to make as much information about the production environment available to the developers as possible. I also worked to make sure the dev environment would mirror production as closely as possible given that we only had one dev sandbox (requests for a staging environment were declined). These two things, combined with being a good teacher, meant I rarely had requests for CLI access to any of our environments.