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 DevOps toolkit and its organizational impact

Viktor Farcic: Moving on to the DevOps toolkit, what tools do you see as empowering workers? Do you think that some tools fit better than others into whatever definition of DevOps people have?

Kohsuke Kawaguchi: In the context of broader automation that goes across a number of different things and this ever-expanding need for automation with human control, the tool is obviously the primary means of enabling automation. I know a lot of Jenkins users see the world that way.

Software developers like myself enjoy inventing tools. That's what we do. So, given that world view, it's only natural that we come up with our own tools to bridge those gaps and expand automation even more, because without automation, you can't create shorter feedback cycles, which is a critical part of DevOps. For me, this is the interesting part. It feels closer to what we can solve, as opposed to the organizational structure problem in enterprises...