I'm not sure I agree with author. Sounds like they have worked at shitty places that are using the word "DevOps" but really they are doing things the old way.

I'm not sure I agree with author. Sounds like they have worked at shitty places that are using the word "DevOps" but really they are doing things the old way. My company practices "DevOps" and it feels great: - Infra team build self-service tools (build, deploy, scale, observe) - Infra team write good documentation for these tools - Dev use tools to build, deploy, and monitor their apps - Dev not use use words like: AWS, k8, Envoy. These are abstracted by tools. - if problem with app (very common) Dev fix it using the tools - if problem with tool (very rare) Infra fix it We have no build engineers, release engineers, etc. However we do have a rotation (similar to on-call) whereby Dev is responsible for releasing code that week. Sure there are sometimes problems, frustrations, etc. No system is perfect. But you are getting paid lots of $$$ so shush with your whining & instead help improve the system. For context my company is mid-size ~150 engineers