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 journey to DevOps

Viktor Farcic: Hi Kevin, you've been involved with many topics that have become central to DevOps since your early childhood working with your father. How did your father's work prepare you for DevOps?

Kevin Behr: Well, it's exactly 30 years since I first got formally involved in the world of computing. In my earlier years, I had the fortune of growing up with my father, Harold Behr, one of the cofounders of the Association of Field Service Managers, or AFSM. For those who don't know, AFSM was one of the first global groups dedicated to global service managers. AFSM would discuss topics that are still related to DevOps today, such as how mainframe computing was going to be serviced, as well as discussing availability and continuity of value for customers.

I was seven years old when I started building small digital computers, working on vacuum tube equipment. I was about ten years old when I started working with midranges and mainframes, in the...