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)

The engineering constant

Júlia Biró: I've had the privilege of working with some very experienced engineers, like yourself for example. I'm also very new at this, but we've already said that technologies change a lot and I am very interested in seeing what is the "engineering constant".

What are the things that will probably come with experience? They're not really knowledge of specific technologies, but skills, thinking patterns, and best practices that can be used overall and don't get outdated. Whether some of those are something that can be picked up to the benefit of my work without having to spend five years learning two or three single technologies in depth. The question from all this is, "What are the things that I can learn without having to spend 10 years in tech, and which will not get outdated?"

Viktor Farcic: You can learn Kubernetes in a year.

Júlia Biró: But Kubernetes will get outdated in around three to five years...