As a former DevOps engineer turned to development, DevOps has been much maligned. The idea is not to get everyone to wear all hats. DevOps makes deployment part of the development cycle rather than the broken practice of throwing code over the wall. Nothing hurts morale like resting soundly each time ops is fighting fires your code created.
DevOps done properly does not require an engineer to deploy her own code, but it does require a sense of ownership over what happens with your code in production. If that means helping someone understand your code changes enough to fix the monitoring tools or tune the database then your product will benefit.
As a former DevOps engineer turned to development, DevOps has been much maligned. The idea is not to get everyone to wear all hats. DevOps makes deployment part of the development cycle rather than the broken practice of throwing code over the wall. Nothing hurts morale like resting soundly each time ops is fighting fires your code created.
DevOps done properly does not require an engineer to deploy her own code, but it does require a sense of ownership over what happens with your code in production. If that means helping someone understand your code changes enough to fix the monitoring tools or tune the database then your product will benefit.
Most importantly, deploying more often means automation gets better. As Martin Fowler keeps saying, "if something hurts, do it more often." (It must hurt him to say that.) http://martinfowler.com/bliki/FrequencyReducesDifficulty.htm...