Point #1 is too real in my org. > Need a database? File a ticket with DevOps. > Need an IAM role? File a ticket with DevOps. > Before long, your massive team o

Point #1 is too real in my org. > Need a database? File a ticket with DevOps. > Need an IAM role? File a ticket with DevOps. > Before long, your massive team of engineers has fully saturated your understaffed “DevOps” team’s backlog. Our DevOps is under IT, not Engineering, so there's already an organizational gap there. I've talked with DevOps multiple times over _years_ and laid out a rough architecture of how Engineering would like to work. To this day after CI/CD passes its still manual deploys with a ticket. Render.com and other platforms do 90+%, if not 100%, of what I want as an engineering manager, but I'm hamstrung by policy and politics that were put in place 6 years ago when non-technology ppl decided we somehow had the resources to manage an OpenStack build instead of AWS. And that's before I realized everything on AWS is config config config and there's entire companies (like Render) that take away most of the work and just give you a dashboard to accomplish what you'd like to accomplish.