30 Days of DevOps Day 13: Misconceptions

Day 13 of 30 Days of DevOps is all about misconceptions:

Share a misconception about ā€˜DevOpsā€™ and your thoughts on it.

What misconception have you chosen?

That somehow you can ā€œbuyā€ DevOps.

If you buy the right tools, release all the time, use the right languagesā€¦ then youā€™re ā€œdoing DevOpsā€, right?

Nope. The honest reflections, continuous improvements, automating away the tedious and repetitive ā€“ seeing DevOps as a more human-centric approach to software development and release, thatā€™s much more important than the products you buy as an organization with the intent to get you magically to DevOps.

1 Like

That you can solve process problems with purely technical solutions.

No chance. Itā€™s people and process first and then using tools and tech to enable those people.

I realise that this can apply to any area of tech really.

3 Likes

Even leading practitioners at DevOps conferences struggle to define ā€œDevOpsā€ so I think that leads to a lot of misconceptions. Anytime I hear someone has a ā€œDevOps teamā€ or ā€œDevOps engineersā€, it raises alarm bells. Itā€™s good to have those to help the team build a DevOps culture and learn practices that help with things like continuous delivery. But creating yet another silo and calling it DevOps is an anti-pattern.

3 Likes

From Twitter I found

1 Like