A good idea plagued by buzzword mentality
The higher-ups in our organization are very buzzword driven, and I imagine they collect a lot of free meals, golf trips and other...amenities...from the DevOps consultants. Just like Agile a few years ago, we've been told that we're now "all in" on DevOps.
What will happen in our case is that we'll take the parts of it that make sense and use it in the real world work we do. We'll even take the single-pane-of-glass magic tools the DevOps company of the month sold them and give a half-hearted effort to integrate them. I think that's the key -- if you let your consultants run the show you're going to get an ITIL-style monstrosity that takes more work to care and feed than the actual work you're doing.
We have a lot of "boring, legacy old school" stuff from 2005 (if you can believe it.) We also have a lot of new cool shiny microservicey stuff. Knowing where to apply DevOps techniques, which ones are appropriate for your world, and what to skip is the key to keep DevOps concepts (which for the most part are really good ideas) from being another shelfware that gets abandoned when the next buzzword comes to town.
Biting the hand that feeds IT
