I would like to point out: DevOps is a failure ---- where you work and how you see it. Just because you play bs bingo for naming things does not change your i

I would like to point out: DevOps is a failure ---- where you work and how you see it. Just because you play bs bingo for naming things does not change your internal processes and no i dont mean the "culture" but the need for the term "SoftOps" because they are "for developers" just explains to me that your org probably has a huge communication problem and that is bad to begin with. Look we use terms like "DevOps" Engineer to explain that we do all things around the stack, but serving the devs is only a tiny tiny part of this. First and foremost our dutys are for the CTO and the Vision. Now the CTO should and does appreciate and use the input of his team to perfect the vision but you get the point. OPS isnt there to serve you or limit your spending either, OPS should take care of compliance in all areas needed and to keep the operation of the org running. DevOps ___for me___ means that the person I am working with can handle the software in the context its being brought up. That includes people operations just as much as the workflows we put in git. It should have been the next level of the Senior Programmers, but since we are truly lacking Programmers that actually do unterstand stack, code and sourrounding requirments, we foget what the term really means. "DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality.[1] DevOps is complementary with Agile software development; several DevOps aspects came from the Agile methodology" (wikipedia.com) its not a synonym for "dude who sets up your cluster"