[ram_rar]

Its a very poorly written article with all the buzzwords one can think of. DevOps is not even remotely close to dead, but rather evolved a lot. Gone are the days, when one could easily ssh into remote prod systems and fix the issue. With shell less Docker images and container orchestration tools (hashicorp stack), CI/CD pipelines, blue-green deployments etc, Devops has become a lot more sophisticated than before.

[hutrdvnj]

> Gone are the days, when one could easily ssh into remote prod systems and fix the issue. With shell less Docker...

I think we finally realized that fixing something in prod via ssh is not a good solution and might introduce new bugs on its own. Rather build an infrastructure that allows you to rollback fast. It is also not worth to fix individual machines in a big cluster, just throw them away and bootstrap them from zero. This way you make sure that you don't have accumulated patches and workarounds on your nodes that might lead to future failures. In some companies we reached the point where you don't even fix a cluster in a multi-cluster setup, but throw away the whole damn thing and bootstrap it from zero.

[cdisnow]

> Its a very poorly written article with all the buzzwords one can think of.

Agreed. Reminds me of articles and blogs that GitLab team publishes these days.

[peakaboo]

You say sophisticated but in reality, it has become extreamly complex, which is a natural consequence of using tons of different tools and glueing them together.

[nosvince]

And that's why there's room for automation to take a lot of the complexity away.

Granted it's not going to be easy to have a platform where every tool can seamlessly connect, but we can start with baby steps such as services that automate multi-cloud deployments like the article suggests.