Gene Kim is a guy who's accomplished a lot more in his career than i have. I kinda-sorta met him in passing at an LSPE Meetup and he seemed like a nice guy. But his recent writeup, "Why We Need DevOps Now", which title i agree with, is just not good at all (i used the word "terrible" on Twitter, which someone called me on, so maybe i'll try to dial back the hyperbole).
As my friend John Willis told me after I dismissed DevOps as just another marketing fad, “DevOps is the best chance at relevance that IT Operations has had in thirty years.” I immediately realized that he was right.
Is that really all it took?
"John, it's a fad."
"Gene, it's our last, best hope."
"OMG UR RITE!!"DevOps is real (
this article says everything that needs to be said about it) and also
a fad, in the same way that Agile Software Development is
real and a fad:

BOSS: "We're going to try something called agile programming. That means no more planning and no more documentation. Just start writing code and complaining." WALLY: "I'm glad it has a name." BOSS: "That was your training."
A good business avails itself of forward-looking approaches in order to contend with the firehose of change that is our industry's lifeblood. But we cannot mistake these approaches for anything other than a tool.
Act I begins with IT Operations, where we’re supporting a large, complex revenue generating application. The problem is that everyone knows that the application and supporting infrastructure is... fragile.
I smell a setup. The scenario described is clearly the result of bad management, who failed to see this sort of undesirable performance down the road and act upon it to preclude the fragility, and it has been that way every time i've encountered it in my career. It is not, as implied, a result of traditional IT operations.
In Act 2, our life gets worse when the business starts making even bigger commitments to Wall Street, often dreamed up by art or creative writing majors
I have no idea what he's talking about here. In my experience, publicly-traded businesses (which would be the ones who make a commitment to
shareholders, not
Wall Street) don't usually have art or creative writing majors making major business commitments; the more likely case is that those positions are staffed with MBAs. Privately held businesses, on the other hand, tend to be beholden to venture capital firms, whose presence can become far more unwelcome and meddlesome than that of your typical shareholder.
We all know that there must be better way, right? DevOps is the proof that it’s possible to break the core, chronic conflict, so we can deliver a fast flow of features without causing chaos and disruption to the production environment.
YOU NEED MANAGEMENT BUY-IN. YOU NEED THE SUPPORT OF THE PEOPLE WHO CONTROL THE MONEY TO HIRE THE RIGHT PEOPLE AND PURCHASE THE RIGHT EQUIPMENT, THE PEOPLE WHO SET THE COMPANY'S EXTERNAL AND INTERNAL STRATEGIES, THE PEOPLE WHO HAVE YOUR BACK WHEN YOU TELL THE COMPANY, "THIS WILL HURT, BUT IN 12 MONTHS, WE WILL NO LONGER LIMP." Painting DevOps as a panacæa does all of us who believe in DevOps and work in DevOps a tremendous disservice. To unfuck a fucked company, you need to fix the culture. This is why Netflix is a shining example — not because of their use of DevOps, but because their culture enabled them to use their talent in a massively constructive and creative fashion.
"Before you can solve a complex problem, you must first have empathy for the other stakeholders."
Before you can solve a complex problem, you must first
understand it. One of the important factors in understanding it is empathizing with the other parties. It is not, however, the
first thing to do.
Perhaps i'm being too harsh on what's less of a thoughtful article and more a plug for his book. But i do not find the appeal in being sold on DevOps by starting off with an elaborate strawman.