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

Bottom-up or top-down?

Viktor Farcic: That's why I think it's very dangerous when you buy into tools that promise certain cultural changes just by existing. In your view, then, what works better: bottom-up or top-down? And more specifically, when there's an initiative, where should it come from?

Chris Riley: I'm going to answer that a little bit differently because I think both questions, in their own ways, are critical. But that being said, if I had to pick one, I would say bottom-up. If you have an issue with bottom-up development, as in you have a developer who's telling you they don't want to focus on building the application and they don't want to get it out the door faster, then you have the wrong developer. If that's your problem, then that presents you with a bigger challenge, because you shouldn't have to explain to a developer why building an application and speed to market are good.

For that reason, when looking at bottom-up versus top...