[igorzij]

Thank you!! And fair point. To us it's in a sense a bet on a particular direction the industry is going to take. If we're right then infrastructure-as-code isn't going away, someone needs to write it, even for the managed services. Those still need to be connected with each other, there are VPCs, security groups, secrets - the "glue" connecting those services. We don't believe developers should care about that though. Specialisation tends to increase, not decrease with time. It's hard enough to make one's frontend or backend work in isolation. So our thinking is that the devops corner of the industry is very much a transitory state - post-problem but pre-product, somewhat like hardware was before the PC, or software development before operating systems. There are strong incentives to cleanly decouple devops from development by means of products - just like operating system engineering is decoupled from software engineering via layers upon layers of apis and tools that don't require any specialist intervention.

So we are trying to make progress in that direction - if managed cloud services were hardware, then we are building an operating system for developers to use that hardware with as little friction as possible.