There are just so many definitions for what DevOps is. It just doesn’t have a fixed definition of any kind.
As the DevOps movement is important to me I’d like to take a moment to help define what DevOps is, if not so much for others, but for myself.
A few good websites that quickly tl;dr’s DevOps are New Relic’s page on the DevOps lifecyle and AppDynamics definition of DevOps through the above acronym, CALMS, or to write it in the negative used by THHGTTG “Don’t Panic”.
That is there are implications when I claim on LinkedIn that I’m a “DevOps advocate”. The first is that I don’t need to have DevOps in the title to be part of a DevOps community. Linux administration as part of the IT workforce is just as much a part of the DevOps movement as the title DevOps engineer. In principal it’s about how the company and its IT workers function. Secondly nothing is perfect, and most companies who see the DevOps light are incrementally designing their work flow to be more in line with a DevOps paradigm, and the simple reason for this is that it works. I aim to be of use in knowing how to properly use technology, but in a manner that will positively affect the dev-ops (-business-client) work flow, which includes stability, high availability, scalability etc. in relation to infrastructure and the part I play in the whole.