Yep. At work, I'm being a bit picky about the wording, but it's shifting people into a better direction. We don't have DevOps people. We have a fairly modern op

Yep. At work, I'm being a bit picky about the wording, but it's shifting people into a better direction. We don't have DevOps people. We have a fairly modern operations team, we have more or less modern developers and tasks or projects follow a DevOps-mindset. Like, if your DBA is attending plannings of teams working on a database heavy project. That is an action following a devops-mindset - breaking up siloed knowledge at the right places in a good way in order to save time on both sides. Weeks of planned work can disappear with the words "Oh there's a postgres extension for this. Give me a week to check it out." Or, if we work on some system so a consultant managing a customers system can roll versions forwards and backwards automatically with a simple UI. Again, something following the devops-spirit of removing yourself from the loop, putting trust into the automation and enabling people to work with less friction. But again, this isn't done by a "DevOps engineer", it would usually be done by one of our operational dudes with a focus on automation and pipelines in close cooperation with the dev-team. It may be picky and pedantic, but it steers thoughts into a better place. And it gives us an answer to "What the hell is ops doing all day?" Making your devs better, and you money, good sir.