If the team building the application is designing the infrastructure, then that's almost the DevOps ideal that orgs dream about. It's really the stuff that happ

If the team building the application is designing the infrastructure, then that's almost the DevOps ideal that orgs dream about. It's really the stuff that happens once you've been launched for a few months that things start to drift. It might start with a redirect rule that isn't in code, an ask to do cost optimization, a security audit. Maybe one dev raises their hand and a few months later they're the DevOps lead with a DevOps team who become the dumping ground for all the non-coding task, on-call, budgeting. Even if your platform is all PaaS and SaaS and serverless, stuff will still break and someone needs to answer the pages.