I don't agree that what we're doing stops at enabling other teams to build. That's part of the role but reducing it to that siloes infrastructure away from othe

I don't agree that what we're doing stops at enabling other teams to build. That's part of the role but reducing it to that siloes infrastructure away from other domains and adds unnecessary friction. You shouldn't have to know about the yamls and the k8s, but you should know about infrastructure concerns and how they relate to you and your design choices, just as infra guys should be aware of what's going on on the front side. Having to work with close-minded counterparts who refuse to elaborate further than "make it work now, or else" is about the worse thing there is. Being willing to participate in good faith in back and forth discussions around those subjects is important and pays dividends.