Book Image

DevOps Paradox

By : Viktor Farcic
Book Image

DevOps Paradox

By: Viktor Farcic

Overview of this book

DevOps promises to break down silos, uniting organizations to deliver high quality output in a cross-functional way. In reality it often results in confusion and new silos: pockets of DevOps practitioners fight the status quo, senior decision-makers demand DevOps paint jobs without committing to true change. Even a clear definition of what DevOps is remains elusive. In DevOps Paradox, top DevOps consultants, industry leaders, and founders reveal their own approaches to all aspects of DevOps implementation and operation. Surround yourself with expert DevOps advisors. Viktor Farcic draws on experts from across the industry to discuss how to introduce DevOps to chaotic organizations, align incentives between teams, and make use of the latest tools and techniques. With each expert offering their own opinions on what DevOps is and how to make it work, you will be able to form your own informed view of the importance and value of DevOps as we enter a new decade. If you want to see how real DevOps experts address the challenges and resolve the paradoxes, this book is for you.
Table of Contents (21 chapters)
20
Index
21
Packt

The role of a DevOps engineer

Viktor Farcic: But if an important component of DevOps is communication between people skilled in development and people skilled in operations, then what the heck is the role of a DevOps engineer? When I look at job descriptions, I think that of the DevOps engineer tops any other profile at the moment.

Wian Vos: Basically, that's just to confuse recruitment.

Viktor Farcic: And the DevOps department as well!

Wian Vos: Imagine, for instance, you and I were going to start a company. We're going to need a DevOps team because we have a burning desire to put out this awesome application. Yet, in our position, we can hire five people. So, the question we have when we're putting together a DevOps team is both, "Who are we hiring?" and "What are we hiring for?"

Are we going to hire DevOps engineers? No. In that team, we want the best application developers, the best tester, and maybe a great infrastructure person and a frontend/backend...