My biggest issue with "DevOps" is that it seems like it should fundamentally be a profession/methodology that rapidly renders itself into obsolescence if its creators and practitioners were actually any good at it.

The whole point is to provide automation, tools, and abstractions that basically make "Ops" fade into the background as a thing you never have to explicitly deal with or have its concerns leaking up to the application in obtuse ways.

It seems to be a thing that should be executed once and then be pretty much done until some entirely new radical kind of computer, network, and/or datacenter innovation happens that completely breaks the mold of how we need to organize machines to run software.

But instead of "DevOps" being this thing where you run the plumbing, test the pipes and valves, and then basically leave the whole thing alone for generations to come; save for inspection (which can be automated) and minor maintenance. "DevOps" seems to often manifest itself as a completely parallel development effort with just as many weird science projects, half-broken integrations, and high rate of change based on chasing some new shiny thing.

Put succinctly, my biggest issue with "DevOps" is that as a marketplace of products, services, and practitioners it seems to fundamentally misunderstand its raison d'être.