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?
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.
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.
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.
From Twitter I found