In defense of DevOps

I will speak from a developer perspective - in a very small team. But we are lucky to be supported by a proactive DevOps team (that is also supporting a load of other dev teams).

The DevOps team has been great and helped us putting good practice in place (terraform in particular). But - as they said to me - my team and I are light years ahead of the other teams. Personally, my take was that the DevOps team probably knows better than I do so that relying on their take is more likely to be a positive outcome that trying my own things.

From my side, long live DevOps. There are enough aspects to maintaining a product that one team can not do it all (let a dev try to do user support!)...

I don't think you have to defend it. In so many use cases software development is more about using the tools and deploying your code right. Operations is often the biggest part of the job and some developers pretend that it's not the case.

OP, don't feed the trolls: DevOps is only dead when people want attention. "Look, I'm edgy, DevOps is dead, now give me my click!"

If anything, WhateverOps is dead. In my opinion, DevOps doesn't have to be separated from DevSecOps, DocOps, or any other trendy badge people make up to seem cool. Over the years DevOps has been proven to be the most efficient way to deliver value to users, and it's one of the easiest way to translate business needs to technical increments.

I agree, it's very difficult to adopt and practice but constantly iterating your processes to cut waste will lead your business to the promised land. Long live DevOps.

I sympathise with your view but also from an outsiders non-tech perspective, I have seen the other side too - pushbacks, inflated egos etc. I don't think DevOps is dead - far from it, it's a sector that is expected to grow in the coming years. But I think if we want to avoid these problems then like @rmondo says below, we need better communication and understanding from both sides.

Thanks for writing this. I agree, DevOps seem to always be in the line of fire but I think that largely comes from non-tech founders/employees not understanding what we do and/or where our job overlaps with other dev roles in the company. As always, better communication/understanding in the company would likely resolve these problems, but in my experience, people don't want to take the time and/or don't have the time to understand.