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)

Culture and collaboration

Viktor Farcic: That's a valid point. In closing, do you have any parting ideas and words, or is there anything that comes to mind that I forgot to ask?

Julian Simpson: No, I think we've covered what I think is most important, which is the culture. I'm super pleased that we haven't really discussed automation or any of the tools, except as examples of something else. To me, DevOps is all about culture and collaboration.

Viktor Farcic: Does that mean the culture shapes the tools or do tools shape the culture, or both? I mean, can you adopt one without the other?

Julian Simpson: My guess is no, because people's expectations must change. I think the tools they use and the culture in which those tools are used are tightly linked. If you could change the culture, then the tools might change consequently, or vice versa. But I think it's more than that.

Lindsay Holmwood did a talk at DevOpsDays 2016 in Wellington, New Zealand, where he pointed...