Originally DevOps was posited as a cultural shift where Devs and Ops teams worked together on both the design of an application and the deployment. It's supposed to be the opposite of "throw it over the wall" where a Dev writes their program, makes sure it works on their laptop/test environment, and then gives some sort of artifact to the Ops team for them to deploy/update. In general though, it's kind of turned into what you experience with devs taking over ops, as long as those ops are "in the cloud."
I come from the other direction, background in ops. My "DevOps" work is automating bare metal server installs, writing tools to make that happen and pretty web interfaces to watch it all happen.
I personally like to think of DevOps as replacing ad-hoc commands and bash scripts with yaml.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Originally DevOps was posited as a cultural shift where Devs and Ops teams worked together on both the design of an application and the deployment. It's supposed to be the opposite of "throw it over the wall" where a Dev writes their program, makes sure it works on their laptop/test environment, and then gives some sort of artifact to the Ops team for them to deploy/update. In general though, it's kind of turned into what you experience with devs taking over ops, as long as those ops are "in the cloud."
I come from the other direction, background in ops. My "DevOps" work is automating bare metal server installs, writing tools to make that happen and pretty web interfaces to watch it all happen.
I personally like to think of DevOps as replacing ad-hoc commands and bash scripts with yaml.