DevOps does not mean that developers are also Ops, like the article seems to be suggesting.
That would be a bit like expecting your house builder to also architect your house. That's not going to happen, but they need to be able to communicate and understand each other.
No, it means that for most companies Ops roles are redundant.
That's why tools like Ansible or Terraform, and the whole Cloud Computing emerged: so that infrastructure can be abstracted away, and you, as a developer who wants to deploy their code to production are only required to create a couple of simple yaml files, trigger the deployment pipeline, and be done with it. Ops roles are outsourced to AWS or other provider.
I know, that's just a theory, real life is nowhere near that ideal state.
because it’s incredibly difficult to build, not to speak of maintaining it. I have seen things close to this, but can’t quite get to the finish line. I’m sure some people are doing it, I guess, but I have yet to see it. a lot of times a team will architect a good, automated solution that works for 3 years untouched and then fails catastrophically because it wasn’t maintained or assumptions start to fail.
this dream of self service devs is becoming a myth. devs do so much incredibly thoughtless stuff to infrastructure all the time. you need an infrastructure person in the process to make it resilient and allow them flexibility to do the stupid shit they want to do - with guardrails.
That would be a bit like expecting your house builder to also architect your house. That's not going to happen, but they need to be able to communicate and understand each other.