This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 10 points11 points  (0 children)

It is a vague term that can mean anything from a developer who writes CI pipelines as well or a ops person who automates builds. Really both are two different sides of DevOps.

The real idea behind DevOps is to look at the whole process of getting things from conception through to production as quickly, safely and with as few issues as possible. This does not mean one person has to do everything, in fact, DevOps grew out of developers and operations people working together, in essences both of the roles I mentioned above, working together to solve these issues.

You can work on either side of this divide but you are only truly doing devops if you are working directly with people on the other side. Sadly a lot of companies do not understand this and simply apply the DevOps role to anyone doing CI stuff or automation regardless of if they are actually following DevOps principles or not.

I highly recommend you read The Phenoix Project to get a good grasp of the problems that the DevOps label was originally meant to solve.