> The teams who lived the dream of DevOps were teams which built their software as cloud native
Or the total opposite. People that not drink the cloud-narrative and the operational simplicity make devops no-brainer.
ie: You are truly made for the massive overenginering of cloud (because you ACTUALLY need that) or you keep things simple enough to fit in a single head.
What is problematic is when you try to do be first, or present to be second.
The immediate following sentence from the one you quoted was:
> This is purely because the PaaS tooling let them efficiently be both Devs and Admins.
It wasn't the cloud which made them successful, it was the level of automation baked into the PaaS solution(s) they built on top of. I thought I was pretty clear on that, but I suppose I could have been more clear.
You could similarly get success if you had an OnPrem solution with really great orchestration layers. And in fact, I've heard of such successes (but not seen up close) of teams doing exactly that with Pivotal Cloud Foundry.
Or the total opposite. People that not drink the cloud-narrative and the operational simplicity make devops no-brainer.
ie: You are truly made for the massive overenginering of cloud (because you ACTUALLY need that) or you keep things simple enough to fit in a single head.
What is problematic is when you try to do be first, or present to be second.