My biggest issue with &quot;DevOps&quot; is that it seems like it should fundamentally be a profession&#x2F;methodology that rapidly renders itself into obsolescence if its creators and practitioners were actually any good at it.<p>The whole point is to provide automation, tools, and abstractions that basically make &quot;Ops&quot; 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.<p>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&#x2F;or datacenter innovation happens that completely breaks the mold of how we need to organize machines to run software.<p>But instead of &quot;DevOps&quot; 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.  &quot;DevOps&quot; 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.<p>Put succinctly, my biggest issue with &quot;DevOps&quot; is that as a marketplace of products, services, and practitioners it seems to fundamentally misunderstand its raison d&#x27;être.