Original link: https://www.hwchiu.com/read-notes-64.html

Title: “DevOps is a failure”
Category: others
Link: https://leebriggs.co.uk/blog/2022/06/21/devops-is-a-failure

The author of this article talks about the meaning and practical significance of the word DevOps from different perspectives

In the first paragraph, the author first chatted about the history of himself and the word DevOps, and the recipient directly threw out a long-term curious point of view of the author: “Everyone must have heard that DevOps is a culture that requires the participation of Dev + Ops, but the author himself participates in DevOps. Related conferences and discussions, most of the attendees are Ops people, not those who are actually involved in the development of Dev people”

period of confusion

The author talked about his experience many years ago. The development team at that time claimed that the team was “true devops”, and at the same time did not discuss various maintenance requirements with the author’s maintenance team. This process made the author very confused, why the other party would say that he It is true devops without finding yourself to discuss maintenance requirements

The author later had a deep chat with the development team and finally understood the meaning of the other party. It turned out that the development team was both development and maintenance. The team used boto3 plus some scripts to manage the life cycle of the application. At the same time, the team recruited “full stack” In addition to the basic back-end technology, engineer” must also have a lot of familiarity and experience with AWS.

The other party’s actions confuse the author even more. After all, the company adopted a Netflix-like approach to build a platform to make it easier for all developers to manage these things, and the development team’s actions were completely the opposite. Why? Want to do this? ?

Pulumi period

When the author joined the Pulumi period, the author began to use some well-known tools such as GitLab, Terraform, Kubernetes and other tools to create a useful platform suitable for developers, but every time I want to promote the platform to developers I always hit a wall , I will always hear such words as “I am not familiar with your things, we are still used to the tools we built ourselves” and so on.

The author continued to try to convince the development team to use the super platform he built, encourage them to participate in DevOps-related activities and other ways, and finally got a reply like “We will try it in our own way~ Thank you”

review

Looking back on the past, the author found that it was himself who was wrong. The vision of DevOps that he had always believed in “let Ops stop saying No, and let Dev stop saying “yo~ deploy today”” is actually not true. The author believes that in 2022 today, the true meaning of DevOps It is “people on the maintenance side try to convince developers to do things according to the ideas of maintenance personnel”

Looking at all the tools that claim to be related to DevOps, you will find that almost all of them are related to maintenance and operations. The skills listed in each DevOps-related job vacancy are also full of maintenance-related skills. For the author, DevOps engineers are related to the past System Admin is not much different at all, the only difference is “build a physical computer room, put a machine on the shelf” vs “build a cloud machine, create a VM”.

There are some ideas of the author in the second half of the article, you can read it if you are interested

The ideas of this article are very interesting. For example, the author mentioned that he wanted to help the development team build a maintenance platform, but he repeatedly encountered obstacles.

Ops may feel that it is inefficient for Dev to repeatedly build tools, and it is better to use a good platform built by yourself
Dev may feel that Ops does not understand their own needs, it is better to build according to their own needs

The same narrative on different scales, such as

dev -> Dedicated development team of 5 people
dev -> 50 dedicated product team

From the latter point of view, you may feel that the team is large enough to handle your own needs, and you do not need to rely on the company to provide a universal platform to handle everything. At the same time, cross-team cooperation may also make many things inefficient and communication costs are too high.

Welcome to leave a message to discuss your ideas

personal information

I currently have Kubernetes-related courses on the Hiskio platform. Interested people are welcome to refer and share, which contains my various ideas about Kubernetes from the bottom to the actual combat.

For details, please refer to the online course details: https://course.hwchiu.com/

In addition, please click like to join my personal fan page, which will regularly share various articles, some are translated articles, and some are original articles, mainly focusing on the CNCF field
https://www.facebook.com/technologynoteniu

If you use Telegram, you can also subscribe to the following channels, where I will regularly push notifications of various articles
https://t.me/technologynote

Your donation will give me the motivation to grow my article

This article is reprinted from: https://www.hwchiu.com/read-notes-64.html
This site is for inclusion only, and the copyright belongs to the original author.