"be the change" I think nails the difficulty of devops and why we end up with the non Devops that we call Devops. Most of us are not Fang companies and don't h

"be the change" I think nails the difficulty of devops and why we end up with the non Devops that we call Devops. Most of us are not Fang companies and don't have the pick of the best engineers in the world (or the region). We cannot trust some of our devs to deploy directly to production because quite simply, some do not understand that responsibility and cannot rise to it. We still need our CTO to check any big changes because things are missed and this just reinforces the idea that you don't have to nail it, the CTO will probably find any problems. We are also in Europe where you can't just fire people if they e.g. deploy 3 bugs to production. So what do you do? Like most companies, you try and introduce a good level of automated testing, some testers to write smoke tests etc. and we don't just deploy whenever like some companies do. Then we are just back where we started with a bit more overhead and still not deploying more quickly to production.