2 min read

No one can seem to agree on what DevOps really is. Although it’s been around for the better part of a decade, it still inspires a good deal of confusion within organizations and across engineering teams. But perhaps we’re all over thinking it?

To get to the heart of the issues and debates around DevOps, we spoke to Viktor Farcic in the latest episode of the Packt Podcast. Viktor is a consultant at CloudBees, but he’s also a prolific author, having written multiple for books for Packt and other publishers. Most recently he helped put together the series of interviews that make up DevOps Paradox, which was published in June.

Listen to the podcast here:

Viktor Farcic on DevOps and agile and their importance in today’s cloud-native world

In the podcast, Farcic talks about a huge range of issues within DevOps. From the way the term itself has been used and misused by technology leaders, to its relationship to containers, cloud, and serverless, he provides some clarifications to what he sees as common misconceptions.

What’s covered in the podcast:

  • What DevOps means today and its evolution over the last decade
  • Its importance in the context of cloud and serverless
  • DevOps tools
  • Is DevOps a specialized role? Or is it something everyone that writes code should do?
  • How it relates to roles like Site Reliability Engineering (SRE)

Read next: DevOps engineering and full-stack development – 2 sides of the same agile coin

What Viktor had to say…

Viktor had this to say about the multiple ways in which DevOps is interpreted and practiced:

“I work with a lot of companies, and every time I visit a company and they say “yes, we are doing DevOps” and I ask them “what is DevOps?” and I always get a different answer.”
This highlights that some clarification is long overdue when it comes to. Hopefully this conversation will go some way to doing just that…
Co-editor of the Packt Hub. Interested in politics, tech culture, and how software and business are changing each other.