DevOps.com

  • Latest
    • Articles
    • Features
    • Most Read
    • News
    • News Releases
  • Topics
    • AI
    • Continuous Delivery
    • Continuous Testing
    • Cloud
    • Culture
    • DataOps
    • DevSecOps
    • Enterprise DevOps
    • Leadership Suite
    • DevOps Practice
    • ROELBOB
    • DevOps Toolbox
    • IT as Code
  • Videos/Podcasts
    • Techstrong.tv Podcast
    • Techstrong.tv Video Podcast
    • Techstrong.tv - Twitch
    • DevOps Unbound
  • Webinars
    • Upcoming
    • On-Demand Webinars
  • Library
  • Events
    • Upcoming Events
    • On-Demand Events
  • Sponsored Content
  • Related Sites
    • Techstrong Group
    • Container Journal
    • Security Boulevard
    • Techstrong Research
    • DevOps Chat
    • DevOps Dozen
    • DevOps TV
    • Techstrong TV
    • Techstrong.tv Podcast
    • Techstrong.tv Video Podcast
    • Techstrong.tv - Twitch
  • Media Kit
  • About
  • Sponsor
  • AI
  • Cloud
  • Continuous Delivery
  • Continuous Testing
  • DataOps
  • DevSecOps
  • DevOps Onramp
  • Platform Engineering
  • Low-Code/No-Code
  • IT as Code
  • More
    • Application Performance Management/Monitoring
    • Culture
    • Enterprise DevOps
    • ROELBOB

Home » Blogs » Doin' DevOps » An Open Letter to DevOps “enthusiast”

An Open Letter to DevOps “enthusiast”

Avatar photoBy: Chris Riley on July 9, 2015 3 Comments

Dear DevOps “enthusiast”,

Recent Posts By Chris Riley
  • Using Incident Response for Continuous Testing
  • What Is Resilience Engineering?
  • Moving from NOC to the SRE Model
Avatar photo More from Chris Riley
Related Posts
  • An Open Letter to DevOps “enthusiast”
  • Taking Stock of DevOps: Where to from Here?
  • DevOps by any other name still gets things done
    Related Categories
  • Blogs
  • Doin' DevOps
    Related Topics
  • CD
  • ci
  • enterprise
  • start up
Show more
Show less

You are confused. But I am confused as well. For approximately two years now this DevOps thing has been both exciting and frustrating. And in ways that are totally different for each of us. At the intersection of all the disparate confusion is the “perfect storm”. What that means for now is that we are all hunkered down in the basement, reading books on “DevOps” to pass the time, and better understand the thing that is attempting to destroy us.

TechStrong Con 2023Sponsorships Available

To start, you are never talking about the same thing. Is it the movement or the function? The function is tactical, and usually defines those who script infrastructure, which is a service too, but still separate from, the rest of the delivery processes. The movement is a mindset, which adds one more layer to the function, people, which some call it by the dreaded name “culture”. All that means is you take control of the culture, and not the other way around. So the movement stack is People, Process, and Tools. In that order, and all together. And it is not a thing, it is a framework. One that focuses you on results. Always improve the pipeline to produce more releases faster, and at a higher quality. But also get to new functionality, not spending time chasing bugs.

Let me count the ways you are confused:

Software Vendors: No, not everyone is already doing DevOps. And certainly not everyone is doing continuous delivery. By the nature of being around the conversation so much you might disagree, but your messaging when only targeted at CI/CD is putting off many of your very relevant prospects.

Developers: Ok I agree IT is annoying. But DevOps does not make them go away. Actually in many ways because you are now more accountable for everything in your code including security, and quality you have more work in addition to your already aggressive backlog. IT can be your friends.

IT: Your job is more than production, it is to keep things moving as well. It is your fault developers are so pissed. You have not already been doing this, DevOps is not ITIL, and you don’t own it, the team does. Really you should think of yourself as a services organization. One which is doing its best to use shadow IT as a roadmap of what to provide. Vet the products, and make them available. Use automation to do the heavy lifting during the day. And find a way to participate in the shared goal of more releases.

QA: The world is changing. And turning a blind eye is not going to work. You actually have many opportunities to push modern development forward with your unique holistic perspective. You see the application and pipeline in it’s entirety. And thus have a lot of insight to offer. But it won’t happen on it’s own. Deliver metrics, and show improvement of the pipeline over time. Move to strategy, and help the developers find bugs before they make it to testing.

But that is not all, your role above is tainted by your organization type Enterprise or Startup.

Enterprises: The sooner you stop fighting modern development, call it DevOps or not, the less painful it will be. And i’m talking serious pain. The kind of pain where you realize that a below average startup, even in a regulated industry, just published an app that is going to change the behavior of your market, and potentially leapfrog you overnight. You could just buy them, because you have the money. But that only further delays the fact that your development team needs to catch up.

Hipster Startups: It is a big world out there. Much bigger than you realize, with a lot of grown up companies, and a lot of rules they have to follow. I know for your environment which is built bottom up DevOps, it is easy to adopt new tools, and use them. Does not mean you should. The “because I can” mentality will not help you grow. Plan ahead, spend some time realizing the challenges of what happens at scale. Focus a little bit on sustainability, not the immediate release. It could just be what keeps you alive.

It would not be fair of me to dish this out, and not talk about my myself and my persona as well. Which I would say contains the DevOps visionaries ( which I am not ), the outside observer (which I am), and the system integrators (who might just save us all). Don’t foster bad market education, and be encouraging. There is a lot of noise out there, that at times can turn people away, especially the enterprise. You dont need to talk about the hype, you need to talk about the results. Be strategi-tactical, teach the why of culture and process, and help organizations use people to execute those processes using great tools. Do not be a process pimp, if you are then remove the word DevOps from your site. Cookie cutter does not work. Help the market in a DevOps kind of way.

Four years from now this letter will be irrelevant. And the modern delivery chain will, just be. But my charter and challenge for you is to make it happen faster, and do not make it a members only club.

Filed Under: Blogs, Doin' DevOps Tagged With: CD, ci, enterprise, start up

« Security at the Speed of Innovation
HashiCorp unites open source DevOps tools with Atlas »

Techstrong TV – Live

Click full-screen to enable volume control
Watch latest episodes and shows

Upcoming Webinars

Evolution of Transactional Databases
Monday, January 30, 2023 - 3:00 pm EST
Moving Beyond SBOMs to Secure the Software Supply Chain
Tuesday, January 31, 2023 - 11:00 am EST
Achieving Complete Visibility in IT Operations, Analytics, and Security
Wednesday, February 1, 2023 - 11:00 am EST

Sponsored Content

The Google Cloud DevOps Awards: Apply Now!

January 10, 2023 | Brenna Washington

Codenotary Extends Dynamic SBOM Reach to Serverless Computing Platforms

December 9, 2022 | Mike Vizard

Why a Low-Code Platform Should Have Pro-Code Capabilities

March 24, 2021 | Andrew Manby

AWS Well-Architected Framework Elevates Agility

December 17, 2020 | JT Giri

Practical Approaches to Long-Term Cloud-Native Security

December 5, 2019 | Chris Tozzi

Latest from DevOps.com

Stream Big, Think Bigger: Analyze Streaming Data at Scale
January 27, 2023 | Julia Brouillette
What’s Ahead for the Future of Data Streaming?
January 27, 2023 | Danica Fine
The Strategic Product Backlog: Lead, Follow, Watch and Explore
January 26, 2023 | Chad Sands
Atlassian Extends Automation Framework’s Reach
January 26, 2023 | Mike Vizard
Software Supply Chain Security Debt is Increasing: Here’s How To Pay It Off
January 26, 2023 | Bill Doerrfeld

TSTV Podcast

On-Demand Webinars

DevOps.com Webinar ReplaysDevOps.com Webinar Replays

GET THE TOP STORIES OF THE WEEK

Most Read on DevOps.com

What DevOps Needs to Know About ChatGPT
January 24, 2023 | John Willis
Microsoft Outage Outrage: Was it BGP or DNS?
January 25, 2023 | Richi Jennings
Five Great DevOps Job Opportunities
January 23, 2023 | Mike Vizard
Optimizing Cloud Costs for DevOps With AI-Assisted Orchestra...
January 24, 2023 | Marc Hornbeek
Dynatrace Survey Surfaces State of DevOps in the Enterprise
January 24, 2023 | Mike Vizard
  • Home
  • About DevOps.com
  • Meet our Authors
  • Write for DevOps.com
  • Media Kit
  • Sponsor Info
  • Copyright
  • TOS
  • Privacy Policy

Powered by Techstrong Group, Inc.

© 2023 ·Techstrong Group, Inc.All rights reserved.