Ah... same old
The Reg is having a fine old time with Dev Ops. Do you know what I've noticed?
"We implemented dev ops for our new start up"
"Try DevOps first on a mobile app"
"Don't get dragged down by the old legacy systems"
DevOps is great, it seems, if you're starting from scratch. If a good number of your staff weren't outsource in the last bout of IT bait & switch, if you can turn off the 30 year old mess of COBOL running on a mainframe for some reason lazy system admins haven't moved over to, er, what's cool now? Ruby or something, running on AWS
Virtualised networking is hard when you've got a 10 year contract to outsource your network support. Virtual storage is hard when you've just shifted all your storage SAs to Uganda.
Not to mention the fact that your devs are earning $5 a day in Manila and are barely able to code, let alone be trusted with admin access to production.
The reason we're all "doing it wrong" is because unless you work in an office with a soft play area, it's impossible to do right on all but the smallest project.
The reason the separation between Ops and Dev exists is Devs are too gung-ho to be trusted with actual live environments and Ops have spent the last 20 years being centralised and centralised so that they can't really know what everything does because there's so much of it, doing so much disparate things