Comment by znpy

> Most of the DevOps folks I’ve encountered, unfortunately, couldn’t code much. So it was mostly ops work with a fancy new title.

The expectations were (and are) irrealistic.

Looking for somebody that has both the software engineering skills of a software engineer and the skills of a sysadmin, willing to do two jobs for the salary of one: yeah sure, keep looking for it.

That being said, i'm one of those that jumped on the bandwagon because in practice it meant fancier job title, higher pay and getting to use newer (often better) tooling.

Ten years ago being a devops engineer rather than a sysadmin usually meant getting to work with EC2 and cloud stuff rather than administering remote physical servers and fighting with NetApp SANs.

Devops was meant to be really a methodology change, not really a job title.

In my experience whether DevOps works or not really depends on the management. I can setup all the automation you want, but management must back me when I tell you're supposed to use the automations rather than involve me into doing your work.

I can surely take feedback and improve whatever you need to be improved, but you *must* be using the automation.

Otherwise we go back and Development and Operations.