(Ignoring the article ATM).<p>Ultimately the &quot;devops&quot; term is widely applied to a bunch of things, usually meaning one or more of:<p>* automating things as much as possible - infrastructure as code, continuous deployment, chatops, etc.
* building tools for your organization to use to run your own infrastructure
* fixing cultural and process problems between development and operations and cutting down on change requests, fixing communication, etc.
* Often, about getting developers to build environments where the code they deploy uses the same automation in dev&#x2F;test as in prod, and more closely resembles prod
* Getting developers to care about production issues
* Getting operations to understand more about development details rather than have a black box they are less likely to understand.<p>Sometimes the title &quot;Site Reliability Engineer&quot; can mean that, sometimes.  Sometimes DevOps means that.  Lately &quot;DevOps engineer&quot; means some mix of infrastructure automation (basically systems administration) and writing a few tools or scripts (often these tools require some degree of coding).  It can get more custom code heavy depending on the organization, but there&#x27;s no real standard.<p>But ultimately, &quot;DevOps&quot; is a (usually confusing) catch-all.  Most &quot;DevOps&quot; conference are really a mix of agile, process, and systems administration topics, and many DevOPs meetups are usually about elevating one&#x27;s game at systems administration and sometimes about Continous Deployment -- though even this can vary.<p>Personally I like the tech parts and don&#x27;t care as much for the cultural parts, having found a lot of it, once heard 4 or 5 times, becomes a bit &quot;preaching to the choir&quot; - i.e. folks know it already.  Which is why I think once you learn the agile&#x2F;process&#x2F;communication bits, the meetups get to be more about tools - these things change and can be new, but there&#x27;s some percieved duty to keep educating the new folks on the cultural stuff (especially as folks may feel some industries that are less startup-like are slower movers, or for folks in large corps that are slower to adopt things).