Well, some orgs need a bridge between dev and ops just like you often have a bridge between devs and sales. As long as communication still flows between the departments, I don't see a problem with having a "DevOps Engineer" position.
That's reasonable, but I disagree. The goal of DevOps is that there should not be separate dev and ops. I strongly believe one team should be responsible for scoping, building, and running the software.
They aren't separated though; I work with devs to address current and potential ops issues at the root. It might sound a bit dysfunctional but it still follows the "second way" from the Poenix Project AFAIK.
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.
Well, some orgs need a bridge between dev and ops just like you often have a bridge between devs and sales. As long as communication still flows between the departments, I don't see a problem with having a "DevOps Engineer" position.
That's reasonable, but I disagree. The goal of DevOps is that there should not be separate dev and ops. I strongly believe one team should be responsible for scoping, building, and running the software.
They aren't separated though; I work with devs to address current and potential ops issues at the root. It might sound a bit dysfunctional but it still follows the "second way" from the Poenix Project AFAIK.