I think some of the article is framed wrong. It's written as competent ops guy/team vs. incompetent developers. But I don't think that's actually what's going

I think some of the article is framed wrong. It's written as competent ops guy/team vs. incompetent developers. But I don't think that's actually what's going on. I'm sure there are competent developers saying the exact same thing about their relatively incompetent ops people. We built a couple relatively simple applications for an enterprise client. It took their ops teams months to get both applications running in K8s, even though our deliverable was a fully functioning container. They were largely incompetent as far as we could tell. But, I don't think it's worth being unkind or judging them. Every time they asked us a question we made an effort to point them in the right direction. There were other times it was a problem we couldn't help with, we kindly let them know that. I think the reality is that the demand for competent IT and developers outpaced supply a long time ago and it's not getting better. Those of us who know and care about the difference should make competent co-workers and executives part of the job evaluation. Or, accept incompetence around you as a reality, help and avoid as wisdom dictates. But, complaining that it exists and framing it as competent ops vs incompetent developers is both untrue and unhelpful IMO. The latter part of the article that talks about the pace of features, complexity, and the lack of time is spot on though IMO. I think the article would have been better focusing here and avoiding the IT vs devs angle.