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)

Exploring the motivations for change

Viktor Farcic: What do you think is driving all of these requests for improvement? Are they driven by the competition or by a genuine interest in new technology?

Ádám Sándor: I think the biggest motivation we see—and what most companies are missing—is the ability to release software fast. They realize that they should release new software every half year, but they need to come to this realization before the competition is already gaining on them and put the proper processes in place early enough so the production pipeline is filled. It's this big pressure in today's market that ends up making engineers leave because, frankly, it's just a horrible environment to work in.

There is also an excitement for new technologies because when companies in the market are looking for engineers, their HR department feels that new recruits will ask, "OK, what technologies are you using?" And when they hear that what...