Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Channels ▼


Other Voices: Is DevOps Subversive?

Jake Sorofman is chief marketing officer for rPath and can be contacted [email protected]

If you follow DevOps, you're probably familiar with the sentiment that this burgeoning movement could have mildly subversive motives. As a solution to the dev/ops bottleneck, one advocate recently proposed:

"Hire wicked smart people and give them all access to root."

While this may be a rally cry for radicals and revolutionaries, it does tend to trivialize roles and processes in IT and probably doesn't engender trust with the mainstream -- nor does it correct the perception that DevOps may breed a cowboy culture.

To be clear, I don't at all believe that DevOps is meant to be subversive. In fact, I believe deeply in the premise of DevOps and see it as a necessary evolution for IT. But I can certainly see how some are led to fear what it stands for.

To some, DevOps seems to minimize principles of governance, repeatability, separation of duties and other good practices of mature IT organizations. To these folks, DevOps seems like the oil to ITIL's water.

I came across a post by John Vincent that does a masterful job of describing why DevOps -- for all its goodness -- collides headlong with certain enterprise realities.

Advocates for DevOps often unwittingly fuel the perception that this worthy movement is one giant end run around traditional IT operations. While I'm certain this is not the intent, we're all familiar with the maxim that perception is reality.

Like many anti-establishment movements:

  • DevOps is super-smart. DevOps focuses on the contributions of the most gifted few to make IT run --the script wranglers, the mavericks and artisans. It often minimizes the fact that genius is neither scalable nor repeatable.
  • DevOps is provocative. DevOps advocacy sometimes pokes its collective finger in the eye of the IT establishment, galvanizing the support of the few who 'get it,' but perhaps alienating those who don't—those who represent the IT majority.

Of course, smart and provocative are not bad things; in fact, they're essential to any movement for change (can you imagine the American Revolution led by passive everymen without conviction and a strong point of view?).

The secret is using smart and provocative as a bridge instead of a wedge.

Today, DevOps is gaining traction in the world of web ops but hasn't found its home in traditional enterprise IT. At the risk of some heckling, I'll go out on a limb and suggest that, for some DevOps advocates, this fact is worn as a badge of honor: Mainstream attention means that DevOps has jumped the shark.

The principles of DevOps are undoubtedly right on: Compounding scale, accelerating change and contracting budgets are forcing IT to the brink. At the same time, public cloud is emerging as a model for the future of IT: self-service, automated and elastic. The universally accepted truth is that IT is under pressure to change. Is DevOps at the heart of this change? I certainly hope so.

But the question remains: Will the revolution take hold or will it become a footnote in history -- a fringe movement that fails to connect with the mainstream?

In my view, the future of DevOps depends upon cooperation with mainstream IT -- perhaps DevOps thought leaders collaborating with (gasp!) ITIL thought leaders.

Maybe there's a way to turn oil and water into peanut butter and chocolate?

I think it's worth exploring. What do you think?

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.