If everything is DevOps, then nothing is DevOps

Tom Healy of Jama Software published a blog entry entitled, “DevOps is Dead, Long Live DevOps” as did Andrey Akselrod and also Nir Cohen. Interestingly, I find these pieces to have related concerns but different reasoning. Clearly, there are naysayers within the IT community that don’t buy into the DevOps fanboi messaging; and that’s okay!

Personally, I believe the IT industry is notorious for taking a good concept, like DevOps, and twisting and contorting it until it fits a consistent model that highlights tooling (product) over outcomes, specialization over generalization, and engineering prowess over simplification. We have seen this same pattern occur with Java, Service Oriented Architecture (SOA), Cloud Computing, and now we see it with DevOps. Ultimately, the downside negative impact is that we lose the support and interest of business as these efforts become more and more technical in nature. Moreover, it feeds an ever increasing cost of operations for IT and minimizes the available pool of candidates for jobs.

Continue reading the full post in JP’s blog.

JP Morgenthal, a distinguished engineer, has been delivering IT services to business leaders for the past 30 years. He is a recognized thought leader in applying emerging technology for business growth and innovation. JP’s strengths center around transformation and modernization processes that leverage next-generation platforms and technologies. He has held technical executive roles in multiple businesses, including chief technology officer, chief architect and founder/chief executive officer. Areas of expertise for JP include strategy, architecture, application development, infrastructure and operations, cloud computing, DevOps, and integration. JP is a published author with four trade publications. Most recently, he is a co-author of “Cloud Computing: Assessing the Risks.”


  1. Tim Coote says:

    Why does IT need business support for adopting DevOps practices? It’s largely a cultural change that did ought to be invisible to the business, other than enabling CD and hence cloud based applications with the benefits of being able to undertake smaller changes, more often at higher confidence and lower cost.

    If anyone’s talking about devops tools, roles or jobs, they’re not talking about devops. As you note/imply, it’s the distortion of meaning by mapping to existing experience that breaks great ideas. Or causes the adoption of poor ideas 😉


  2. jpmorgenthal says:


    You have actually validated my message through your response. To you, it’s largely a cultural change. That is not the case for everyone. I tweeted over the weekend “His DevOps isn’t their DevOps isn’t my DevOps”. Your perspective is that DevOps is solely within the scope of IT. If you look at it from the perspective of Phoenix Project, getting the business to commit to freezing certain projects was critical to allowing the CIO to reprioritize and turn things back on in a manageable way and deliver the new e-commerce site.



  3. Great post, most informative, didn’t realise devops were into this.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: