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 lightbulb moment

Júlia Biró: I was born and raised in Hungary and trained as a mathematician. I wanted to see if I could take my favorite subject from school and turn it into a career. That turned out to be not such a smart idea. I was not cut out to do math as a career, and I found myself being more interested in the more practical problems. Because of that, in the end, someone suggested that I might want to learn programming, and this is how I gravitated towards the IT sector.

Once I was committed, I started training as a software engineer, and eventually, I was lucky enough to join a wonderful company called Prezi, where I was a very junior engineer placed on the infrastructure/DevOps team. It was as if a light bulb had switched on within me. I suddenly found myself knowing that this kind of engineering was what I wanted to do, and from that moment three and a half years ago, I would say I became a DevOps engineer.