devops工程师_为什么要将DevOps精神带给非工程师？

devops工程师

This article was sponsored by PagerDuty. Thank you for supporting the sponsors who make SitePoint possible!

本文由PagerDuty赞助。 感谢您支持使SitePoint成为可能的赞助商！

In college, I was part of a student body that managed an intranet portal. One of our biggest issues was recruitment. My team of about 35 first organized a written test for over 400 people, of which 50 made the shortlist. Then we painstakingly interviewed these applicants to arrive at our final selections of about 15. Those involved in the selection collaborated through email, and the process took a few nights.

在大学里，我是管理Intranet门户的学生团体的一部分。 我们最大的问题之一是招聘。 我的大约35人的团队首先为400多人组织了笔试，其中50人入围。 然后，我们经过艰苦的采访，最终确定了大约15位申请人。最终选择者通过电子邮件进行了协作，整个过程花了几个晚上。

It was a tedious process, but can you think of a way to improve it? Keep that question in mind as I will come back to it later.

这是一个繁琐的过程，但是您能想到一种改进方法吗？ 请记住该问题，因为稍后我会再讨论。

好日子 (The Good Ol’ Days)

Email has become a crucial tool with all sorts of uses beyond basic communication. We’ve all used it as a way to manage tasks, as a de facto forum, as a place for reminders, or even as cloud storage (have you ever emailed yourself an important document?). Development teams communicated through email lists. Code patches were shared over email too. With the emergence of new technologies like website downtime monitors and CRM software, those alerts were shared over email too.

电子邮件已成为除基本通信以外的各种用途的重要工具。 我们所有人都将它用作管理任务的方法，事实上的论坛，提醒的地方，甚至甚至是云存储(您是否曾经给自己发送过重要文件的电子邮件？)。 开发团队通过电子邮件列表进行沟通。 代码补丁也通过电子邮件共享。 随着网站停机监视器和CRM软件等新技术的出现，这些警报也通过电子邮件共享。

Email providers evolved as well, providing us with tags and filters to better manage our inbox. However, this was only a temporary stopgap, and we soon reached a point where email became overwhelming — there were too many emails and too little time.

电子邮件提供商也在不断发展，为我们提供了标签和过滤器，以更好地管理我们的收件箱。 但是，这只是暂时的权宜之计，我们很快就达到了使电子邮件变得不堪重负的地步–电子邮件太多，时间也太少。

Source – Grammarly

资料来源– 语法

输入DevOps (Enter DevOps)

After outlining the cracks that develop when we try to manage everything over email, let’s answer the question: Why did we overuse email in the first place?

在概述了我们尝试通过电子邮件管理所有内容时出现的漏洞之后，让我们回答一个问题： 为什么我们首先过度使用电子邮件？

I believe the answer can be found through an analogy: the use of smartphones in our daily lives. Smartphones are now devices we can’t live without. Whether it’s connecting to friends, taking selfies, paying bills, setting alarms, managing to-do lists, ordering food, booking tickets, shopping — modern smartphones do it all, every day.

我相信可以通过类比找到答案：在我们的日常生活中使用智能手机。 现在，智能手机已成为我们不可或缺的设备。 无论是与朋友交流，自拍照，支付账单，设置闹钟，管理待办事项，订购食物，预订机票，购物，现代智能手机每天都能做到。

As humans, we prefer using a single handheld device to perform all our actions because we prefer the idea of singularity — a single medium that helps us in all our tasks. That is the reason we used email for everything — managing all activity through a medium on a single screen is simpler that ranging over different media.

作为人类，我们更喜欢使用单个手持式设备执行所有操作，因为我们更喜欢奇异的想法-单一的媒介可以帮助我们完成所有任务。 这就是我们将电子邮件用于所有内容的原因-通过单一屏幕上的媒体来管理所有活动比在不同媒体上进行管理更为简单。

To answer our original question, email served as a medium to connect everything else and joined them together. Looking at the world of web development, we used email to connect the different parts of development of a web application — from understanding the requirements through discussions, coding and testing, automating the code deployment process to analyzing the feedback of the end users. This is where DevOps comes in.

为了回答我们最初的问题，电子邮件充当了连接其他所有事物并将其结合在一起的媒介。 纵观Web开发的世界，我们使用电子邮件连接了Web应用程序开发的不同部分-从通过讨论，编码和测试来理解需求，使代码部署过程自动化到分析最终用户的反馈。 这就是DevOps的用武之地。

DevOps is a portmanteau of the words “developer” and “operations”. The idea of DevOps is to merge the whole development and system administration process into one that functions seamlessly and efficiently. At its center is proper collaboration between teams and processes through communication and the use of the right tools.

DevOps是“开发人员”和“操作”这两个词的写照。 DevOps的想法是将整个开发和系统管理过程合并为一个无缝且高效运行的过程。 通过沟通和使用正确的工具，团队和流程之间的适当协作是其中心。

大！ 下一个是什么？ (Great! So What’s Next?)

Imagine an organization that works on a latest web technology. First, it needs to ensure a service is created, keeping in mind the exact requirements. The alpha and beta phases of the product are then created and launched. Once the product is off the ground, patches are then released to enhance the features of the product. There are many bottlenecks in this process, like the product not being up to the expectations or the presence of unexpected bugs in releases. DevOps is about finding those bottlenecks and fixing them with increased collaboration.

想象一个使用最新Web技术的组织。 首先，它需要确保创建服务，同时牢记确切的要求。 然后创建并启动产品的Alpha和Beta阶段。 产品停产后，将发布补丁以增强产品功能。 在此过程中存在许多瓶颈，例如产品未达到预期的期望或版本中存在意外错误。 DevOps致力于发现这些瓶颈，并通过增强协作来解决它们。

You may say your team is already working efficiently. Why then should you introduce DevOps in an already established organization? Perhaps you’re already using DevOps principles without giving it a title. It’s all about looking for bottlenecks in the status quo, introducing DevOps principles to fix those bottlenecks, and then measuring how DevOps made the whole process more efficient.

您可能会说您的团队已经在高效地工作。 那么为什么要在已经建立的组织中引入DevOps？ 也许您已经在使用DevOps原理而没有给它一个标题。 这一切都是为了寻找现状的瓶颈，介绍DevOps原理来解决这些瓶颈，然后评估DevOps如何使整个过程更高效。

Let’s take a look at three places, beyond software development and system administration, where a DevOps approach could drastically improve processes.

让我们看一下除软件开发和系统管理之外的三个地方，DevOps方法可以极大地改善流程。

1.更聪明的招聘 (1. Smarter Hiring)

Source- Startups.co.uk

源- Startups.co.uk

Let’s revisit the example of the hiring process I mentioned in the introduction. The process of hiring is a hectic one — and rightly so. If you want the best people to work for you, you need to be able to sort out the best talent from the lot, and this isn’t easy. In web development-related roles, a resume shortlisting is usually followed by a coding test, group discussions and one or more rounds of interviews. Obviously, the same group of people may not be handling all of these — especially if the number of requirements is high.

让我们回顾一下我在引言中提到的招聘过程的示例。 招聘过程很忙-是的。 如果您想让最优秀的人才为您工作，那么您需要能够从中选拔出最优秀的人才，这并不容易。 在与Web开发相关的角色中，通常在简历入围之后进行编码测试，小组讨论和一轮或多轮面试。 显然，同一批人可能无法处理所有这些问题，尤其是在要求数量很高的情况下。

The bottleneck in this process is the communication time between each stage. Implementing DevOps principles could perhaps help make the process more efficient by a long way, with team members able to communicate centrally and share their thoughts and responses to given candidates.

此过程的瓶颈是每个阶段之间的通信时间。 实施DevOps原则也许可以从长远来看帮助提高流程效率，使团队成员能够集中交流并分享他们对给定候选人的想法和回应。

2.更多动态的营销团队 (2. More Dynamic Marketing Teams)

If you look closely at Quora, you’d see that it’s basically a form: a platform where people ask questions and others answer them. In terms of functionality, it’s probably the same as any other forum like Yahoo Answers (Yahoo Answers also had the gamification system like Quora). The popularity of Quora can be attributed to one important thing — marketing.

如果仔细研究Quora，您会发现它基本上是一种形式：一个人们提出问题而其他人回答问题的平台。 在功能方面，它可能与任何其他论坛(例如Yahoo Answers)相同(Yahoo Answers也具有Quora这样的游戏化系统)。 Quora的受欢迎程度可以归因于一件重要的事情-市场营销。

Marketing is an umbrella term for a wide range of activities — from doing market research, advertising, developing and repositioning a brand to evaluation reactions of customers to changes in the product lines and much more.

营销是各种活动的统称-从进行市场研究，广告，开发和重新定位品牌到评估客户对产品线变化的React等等。

DevOps can help build a connection between teams focussed on research, branding, customer management and sales. Rather than distributing your conversations between a variety of communication channels and restricting it to a subset of your marketing, work along DevOps principles and work in a more collaborative, open way, and use iterative strategies to develop campaigns and creative material.

DevOps可以帮助在专注于研究，品牌，客户管理和销售的团队之间建立联系。 与其在各种沟通渠道之间分配对话，而不仅仅是将其限制在营销的一个子集上，不如遵循DevOps原则，以一种更加协作，开放的方式开展工作，并使用迭代策略来开发活动和创意材料。

3.更快乐的设计师 (3. Happier Designers)

The process of designing when developing a web application is not simple. After a long conceptualization process, a first draft of the design is completed. It’ll then go through an approval phase, which might involve multiple people, each with their own (often conflicting) feedback. Then, the design is implemented and tested before it goes live. This staggered approach is not too far away from the kinds of open, iterative approaches DevOps encourages.

开发Web应用程序时的设计过程并不简单。 经过长时间的概念化过程，完成了设计的初稿。 然后，它将经历一个批准阶段，该阶段可能涉及多个人，每个人都有自己的(通常是相互矛盾的)反馈。 然后，在上线之前对设计进行实施和测试。 这种交错的方法与DevOps鼓励的开放式迭代方法相距不远。

A more formal introduction of the philosophy of DevOps could help in increasing collaboration, saving time and leading to higher productivity. An iterative approach, where ideas are developed over time and according to feedback starting with simple concepts and moving to more fully-realized products, would also serve designers well. Constructive feedback, given early and often, may reduce the amount of last-minute revisions further down the line.

对DevOps哲学的更正式的介绍可以帮助增加协作，节省时间并提高生产率。 迭代方法可以使设计师随着时间的流逝并根据从简单概念开始的反馈逐步发展思想，然后转向更全面实现的产品。 尽早且经常给出建设性的反馈意见可能会减少最后一刻的修订量。

转移到DevOps (Shifting to DevOps)

Does the idea of DevOps sound exciting? Maybe you are already using it to a certain extent in your team.

DevOps的想法听起来令人兴奋吗？ 也许您已经在团队中某种程度上使用了它。

There are many services out there which can help you seamlessly bring in the DevOps spirit. One such service is PagerDuty, simplifying incident management for your team.

有很多服务可以帮助您无缝地融入DevOps精神。 PagerDuty就是这样一种服务，它可以简化团队的事件管理。

Changes to the way your team works can sometimes face resistance. However, you are perhaps not going to feel the shift as there are many tools which make the process easier. For instance, if you use emails to manage incidents, PagerDuty provides an email parser to scan incoming emails for information. If your team prefers handheld devices instead, these native mobile apps ought to do the trick.

团队工作方式的更改有时可能会遇到阻力。 但是，您可能不会感觉到这种转变，因为有许多工具可以使过程更轻松。 例如，如果您使用电子邮件来管理事件，那么PagerDuty提供了一个电子邮件解析器来扫描传入的电子邮件以获取信息 。 如果您的团队更喜欢手持设备，那么这些本地移动应用程序应该可以解决问题。

On the other hand, if you prefer chat applications to manage team communications, you would perhaps find the idea of an integration of DevOps and instant messaging promising. This pairs the ephemeral nature of chat, with the advantages PagerDuty brings (longer-lasting and searchable information, to name just two).

另一方面，如果您更喜欢使用聊天应用程序来管理团队沟通，则可能会发现DevOps与即时消息集成的想法很有前途。 这将聊天的短暂性质与PagerDuty带来的优势(持久和可搜索的信息，仅举两个)相结合。

最后的想法 (Final Thoughts)

DevOps is a revolutionary idea, which challenges the traditional boundaries of team dynamics, and you need courage to bring about such change! If you’ve decided to take a leap of faith and try out the DevOps principles, I wish you luck.

DevOps是一个革命性的想法，它挑战了团队动力的传统界限，您需要勇气实现这种改变！ 如果您决定大胆尝试并尝试使用DevOps原则，祝您好运。

Are you considering taking the plunge into a DevOps workflow? Or are you ahead of the curve and using DevOps principles already? Let us know in the comments!

您是否正在考虑投入DevOps工作流程？ 还是您已经走在前面，已经在使用DevOps原理？ 让我们在评论中知道！

翻译自: https://www.sitepoint.com/bring-devops-spirit-non-engineers/

devops工程师