Dunno, in my experience there is a long tail of use-cases where it is a more practical to work closer to system level (for different reasons: less complexity, p

Dunno, in my experience there is a long tail of use-cases where it is a more practical to work closer to system level (for different reasons: less complexity, political issues, legacy systems, etc.), so I don't think it's as black and white as you make it out to be. But I agree that there is a threshold after which 'everything API' is the way to go. Where that threshold is if often guesswork. Overall, I don't think our tooling is quite there, and we haven't found the right abstractions yet. Terraform and Pulumi are nice enough, but to me it looks like they are only treating the symptoms, instead of looking at the issues on a more holistic level. I don't have any good solution for that, but I think we'll need to try to look at everything we're doing from different perspectives than the ones we are used to. That's hard (at least for me), and it's getting harder the deeper we dive into the current layers of complexity wrapped into more complexity.