Episode Details

Some of the highlights of the show include: 

• The difference between cloud computing and cloud native.
• Why operations teams often struggle to keep up with development teams, and the problems that this creates for businesses.
• How Dave works with operations teams and trains them how to approach cloud native so they can keep up with developers, instead of being a drag on the organization. 
• Dave’s philosophy on introducing processes, and why he prefers to use as few as possible for as long as possible and implement them only when problems arise. 
• Why executives should strive to keep developers happy, productive, and empowered. 
• Why operations teams need to stop thinking about themselves as people who merely complete ticket requests, and start viewing themselves as key enablers who help the organization move faster. 
• Viewing wait time as waste. 
• The importance of aligning operations and development teams, and having them work towards the same goal. This also requires using the same reporting structure. 

Links:

• Company site: https://www.mangoteque.com/
• LinkedIn: https://www.linkedin.com/in/dmangot/
• Twitter: https://twitter.com/DaveMangot
• CIO Author page: https://www.cio.com/author/Dave-Mangot/

Transcript

Announcer: Welcome to The Business of Cloud Native podcast, where we explore how end users talk and think about the transition to Kubernetes and cloud-native architectures.

Emily: Welcome to The Business of Cloud Native. I'm your host, Emily Omier, and today I am chatting with Dave Mangot. And Dave is a consultant who works with companies on improving their web operations. He has experience working with a variety of companies making the transition to cloud-native and in various stages of their cloud computing journey. So, Dave, my first question is, can you go into detail about, sort of, the nitty-gritty of what you do?

Dave: Sure. I've spent my whole technical professional career mostly in Silicon Valley, after moving out to California from Maryland. And really, I got early into web operations working in Unix systems administration as a sysadmin, and then we all changed the names of all those things over the years from sysadmin to Technical Infrastructure Engineer, and then Site Reliability Engineer, and all the other fun stuff. But I've been involved in the DevOps movement, kind of, since the beginning, and I've been involved in cloud computing, kind of, since the beginning. 

And so I'm lucky enough in my day job to be able to work with companies on their, like you said, transitions into Cloud, but really I'm helping companies, at least for their cloud stuff, think about what does cloud computing even mean? What does it mean to operate in a cloud computing manner? It's one thing to say, “We're going to move all of our stuff from the data center into Cloud,” but most people you'll hear talk about lift and shift; does that really the best way? And obviously, it's not. I think most of the studies will prove that and things like the State of DevOps report, and those other things, but really love working with companies on, like, what is so unique about the Cloud, and what advantages does that give, and how do we think about these problems in order to be able to take the best advantage that we can?

Emily: Dive into a little bit more. What is the difference between cloud computing and cloud-native? And where does some confusion sometimes seep in there?

Dave: I think cloud-native is just really talking about the fact that something was designed spe