Since DevOps began being implemented within companies, one of the concepts brought together was its fundamental culture.
Which leads us to the question: what is DevOps culture? According to this Atlassian article:
At its essence, a DevOps culture involves closer collaboration and shared responsibility between development and operations for the products they create and maintain. It helps companies align their people, processes, and tools toward a more unified customer focus.
Realistically, embedding DevOps culture within companies can sometimes be difficult to implement. This can be due to many factors, including how adopting a new culture can be challenging for staff who are used to the current way of working.
However, Google has shown how software delivery can be faster by using DORA metrics, which is a part of this culture.
Still, developers want to showcase better performance and have functional and efficient workflows to deliver their code faster between the environments without needing to dive deep into a complex operational side of things. In addition to this, they will need to familiarize themselves with topics like cluster management, sysadmin and so many others.
So how can we find a resolution to this? Well, there are many options like DevOps as a Service or a Developer Control Plane, which focuses primarily on the developer experience and enhancing its performance overall with software delivery and tooling.
If you are interested in learning about Developer Control Plane, I invite you to read this article.
Now, what do you think about DevOps culture? Do you think this is one of those beautiful concepts on paper that might not be practical when actioned? Let's discuss it!
Top comments (4)
Our company works with Azure DevOps and we are also only hired if we have both Dev and Ops experience.
But it is totally possible for someone to be good at coding, but never have used Docker in tandem with OpenShift for example. I had to learn all of that on the job as well.
But that is where the double edged sword is. You want people to have some knowledge but it's hard to come by when you ask for specific tools.
What they did in our company is just ask if you have any prior experience in Ops and if you are willing to learn new tools. If that answer is yes you are already likely to be hired as we have a shortage in the Netherlands of developer for almost every language.
That’s cool! This is also an excellent way to manner the operational side by including people interested in this subject. Plus, those people may have a development background already and want to learn about the Ops of the DevOps word, so in that way, you have the best of both worlds!
By the way, you can also check out our developer control plane. It is meant to solve the challenges of developers trying to handle Ops by eliminating the need to learn more tools and automating workflows from build to deployment.
Culture is from the world cult. For any cultural element to be successful, it needs to be engrained as a standard and chiseled into the minds and souls of the people involved. Not struggling with implementing DevOps would mean the majority(not just technical) to invest their minds in the concept and be conscious of practicing it. Right here is where the problem lies. DevOps would have been easier if it were about tools than people. Many people are more focused on actual work than improving daily work or their approach to work as they think the former pay the bills unless the company finds a way to reward the latter.
I totally agree! For a culture to be successful, patience is crucial. Because it doesn’t come just from one day to another, it needs time. And by practicing, the best way to get into it is by creating the habit or finding other solutions. Because if it’s a startup or a company that wants to escalate their project faster, time compromises them, and that’s where maybe delegating this process can be the key to success.
Interesting that you mention the need to focus on tools rather than people, maybe check out our Developer Control Plane in your free time. I will be happy to hear your thoughts on this tool.