[signal]

I disagree. I think the article speaks rather well about what DevOps is really about. There's actually a great deal of consensus within the community about it's meaning, and Mr. Kim has been a major contributing member for quite some time now. Every DevOpsDays since 2009 has critiqued and reaffirmed the ideals and principles. Have a look at vimeo.com/devopsdays or the wikipedia article for DevOps.

Swapping DevOps for PostOps or NoOps or FooOps doesn't change what it means.

Recruiters and managers starved for multidisciplinary, highly skilled T-shaped staff have started to throw the term around in job descriptions, but misuse of a term doesn't change it's meaning until the majority of its users adopt the evolution.

[pollockgf]

You're both right, and that's what is holding DevOps back. From a prescriptive view of language, "DevOps" has the meaning that early leaders like Gene Kim gave it: a culture of collaboration and continuous improvement that combines dev and ops teams. From a descriptive view of language, LOTS of people, and not just recruiters, use it to mean a special group of people who are essentially release managers. Is DevOps the union or intersection of dev and ops? It really depends on what you want it to mean. And that is...not useful.

[signal]

So here's what that actually is: DevOps is super popular with recruiters and managers since the venn diagram of people who care about DevOps tend to be good team players with general yet current competency with very valuable tools and techniques, and they happily pay very well for these people. People who like being paid very well and enjoy working interesting and current problems realize this and thus DevOps is a tag that allows these two groups to find eachother. It absolutely gets misused in job titles for visibility, and we don't care because it usually doesn't mean the company wants a person who knows and does everything (though it certainly happens). It is entirely possible for DevOps to refer to a position, but by the very nature of the contraction, it would be two jobs for one person. Right now we live in a time of sufficient complexity such that in all but the smallest organizations that doesn't make sense, and in those organizations job titles are moot anyways.

In reality, if you look at the history of the term and the current leadership of the development and discussion around DevOps, it still represents the following core areas: 3rd Order Cybernetics, Agile (Infrastructure + Software Development) and Continuous Delivery. I personally believe it's just a simpler way to refer to 3rd Order Cybernetics (3OC will never catch on) and DevOps the term will give way to something that better fits the nature of the movement, but until then, that's what DevOps is. I agree there's a lot of noise and confusion, but that hasn't erased the history, the progress or the true current state.