Remembering the ideas from DevOps at its inception, the point was to remove the friction between developers and operations: have operations stop saying “no” and

Remembering the ideas from DevOps at its inception, the point was to remove the friction between developers and operations: have operations stop saying “no” and developers stop saying “yolo lets ship it”. Well, that's pretty much doomed to fail by design. If you are on the engineering team and not writing features that deliver direct value to the company, wtf are you doing? You're damn right as a dev I expect to "Yolo" it if you're getting paid to make operations safeguarded, streamlined, and resilient to downtime. I don't literally mean I intend to be sloppy, and there are some great tools (esp. on CI and alerting frameworks) that the DevOps culture built, but I can buy that as a service. If you are on DevOps and you are not accelerating devs in the only way that matters to the business (velocity of features with fewer bugs), then what the hell are you doing? Scale should be my problem as a dev to be concerned with because I have deep knowledge of the use case, and should know my stack. I'm sorry to sound harsh, but IME, DevOps people have a terribly inflated view of their contribution to a company's bottom line. Devs are an awfully scarce resource, and these guys are often more than capable of producing real value to drive a business, but they seem hell bent on spending it on derivative, second order concerns that just aren't really that important to employer.