This article can be summarized as this “one day developer got mad at devops/sysadmin(who makes sure email, containers, access to serverless Lambda,etc are up and running and packets are inbound and outbound to AWS/Azure/Heroku are flowing properly and secure) and decided there should be NoOps :)

The end story of NoOps is ending on a newspaper with a security breach and calling three letter companies for help, or lawsuits from investors if there are any for negligence…nice try though. There won’t be such a thing NoOps until all developers start fixing vulnerabilities in their code.