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 difference between the self-taught engineer and the schooled engineer of today

Viktor Farcic: Switching gears, you mentioned that you started with computers when you were seven. Do you have any thoughts about the difference between the self-taught engineers or schooled engineers of today? More broadly speaking, how do you see education in today's world?

Liz Keogh: I didn't know what I didn't know. Back then, I was a little bit more disciplined than a hacker. I have a fairly ordered mind when it comes to programming, so I got taught how to test my software, and I very quickly realized I was second-guessing myself if I wrote the tests afterward. At first, I was writing the tests around empty interfaces, and just making them compile, which, of course, is a lot like TDD now. There were no IDEs back when I started professional coding. We were all working in whatever text editors we had. I think it was Vi or Emacs or something like that, and you compiled on the...