Sitemap

The DevOps Defence. There can’t be “no culture” on project. When “everything is bad” it’s just a kind of culture

4 min readMar 14, 2023

There is a lot of the criticism around the DevOps approach nowadays. I wrote the article to clarify the main points. Let’s look at the confusion in the industry around this term, touch on the interesting question “When will DevOps leave the market?” and discuss when there is no DevOps approach on the project.

The DevOps approach was shaped by experienced market engineers, just like Agile for example. Due to the increasing projects complexity and market competition, it became clear in a practical way, that the values of Development and Operations teams needed to be combined. This was only one of the causes of the DevOps movement.

The DevOps definition below is better to memorise if you are reading it for the first time. The phrase “no one can formulate what it is” will not work in interviews at mature world-class companies.

DevOps is a set of practices, tools, and a cultural philosophy that automate and integrate the processes between software development and IT teams. It emphasizes team empowerment, cross-team communication and collaboration, and technology automation.(https://www.atlassian.com/devops)

(Amazon AWS: What is DevOps? https://aws.amazon.com/devops/what-is-devops/, Atlassian: What Is DevOps? https://www.atlassian.com/devops, Google DevOps: https://cloud.google.com/devops, https://ru.wikipedia.org/wiki/DevOps etc..)

Indeed, the fact that DevOps is a set of practices aimed at “something” is difficult to perceive. And at first there was no exact definition. The Agile approach (methodology) had the same problem of perception. In my opinion, the most notable confusing issues in DevOps understanding are:

1. At the very beginning, the market did not have an exact definition of what DevOps is.

2. The difference between the regions of the IT industry

3. Different project scales

The difference between the regions of the IT industry

The market brings different requirements and expectations to engineering positions. SRE found itself in the same situation. In the first book Google engineers wrote, that SRE — is primarily a developer who is well able to monitor and maintain his code in PROD. Now, often, SRE is a separate position not related to development.

Get Aleksei Fedorov’s stories in your inbox

Join Medium for free to get updates from this writer.

In the US market, developers are often responsible for DevOps practices, while in the CIS market, DevOps is often handled by Ops engineers (SysAdmins). Thus the question “What is DevOps for you?” had the right to exist.

Different project scales

Sometimes the question is “what exactly does SysAdmin/Operations do?”. The question also has a right to exist and is often asked by engineers of small business/services.

For example, there is a small online store selling one Ferrari per month. For such a store, the simplest but fantastically beautiful Frontend is enough. After handing over such an online store to the end business owner and going live, one or two programmers are enough to release new features.

In comparison, for a media platform like Youtube for only one player, you need a fleet of servers with different roles. Then servers/services responsible for high load, fault tolerance, load balancing, etc. will be added. Processes of building and deploying code, automating and maintaining infrastructure on such projects can take a lot of resources and expertise. It’s not that it’s a problem or uninteresting. Usually developers are busy writing features or the main code of the service and not maintaining automation for CI/CD and infrastructure. But the question “what exactly does SysAdmin/Operations do?” on such projects disappears.

When do we not have DevOps in a project?

To better understand the DevOps definition, you can look at the question from the other side: when do we not have DevOps?

  • if there is no cross-functional team (For example, you write the Linux kernel. Then, you are simply a system programmer who needs CI to be configured for teamwork to reduce time integration costs during merging)
  • if there is no Time To Market (No need to deliver fast new features to users)
  • if there is “no culture” (This is language trap. There can’t be “no culture” on project. When “everything is bad” it’s just a kind of culture. I’ll give a simple example: the team does not share responsibility for values. For example, for Dev it can be frequent feature releases and for Ops — PROD stability). In a cross-functional team, we share responsibility.

When will DevOps leave the market?

Just like Agile, Scrum or ITIL, DevOps has formed a maturity model and is moving into a default approach (PMI Defining DevOps, ITIL® 4 and DevOps White Paper). When Scrum appeared, everyone “implemented” it, underwent lengthy trainings, bought books, shared their experience. Now joining the Scrum team, it is enough to read how the Scrum framework is implemented on one sheet.

You can look at the path of DevOps through the technology maturity cycle. The market regulates the process and DevOps moves from the top of the hype to the plateau of real demand as the default standard. You saw this process relatively recently with BigData. Now artificial intelligence is moving along a similar curve.

Press enter or click to view image in full size
https://en.wikipedia.org/wiki/Gartner_hype_cycle

We can say that DevOps is becoming less noticeable, but it does not disappear anywhere, gaining a foothold in its market segment. The speed of learning practices and approach becomes faster and more accessible. I wonder what the next round of development of the industry?

--

--