Is your DevOps title “hip”? What does it mean? Does it matter? In this episode, the gang discusses the fundamental differences between dev ops positions based on “hipness”, as well as if it actually matters in today’s world.
Will needs some developer therapy, and maybe you do, too. In this episode, Will talks about reconfig issues he’s having with a client, and his loyal compadres help him find the light at the end of the tunnel.
Ready to add another tool to your toolkit? In this episode, the squad sits down with AWS connoisseur, Stephen Kuenzli. They lay out how to make integrating IAM a breeze, the EXCITING future of AWS, and why AWS hasn’t asked you this ONE question that, frankly, you should have asked already.
Ready to pull the plug and go server-less? Hold your horses. In this episode, the DevOps fellows sit down with Allen Helton, a developer knows all about server-less ops. They discuss the biggest pros and cons for going server-less, why you HAVE to start with the big “A” to keep everything neat, and the NUMBER ONE mistake developers make when trying server-less for the first time.
We’re not calling you a dummy, but you might be one if you don’t listen to this episode. This time around, the gang discusses the do’s and don’ts of choosing CI/CD tools, including how to safety migrate between them, why super-specialized tools are getting extremely popular this year, and the ONE component that makes or breaks a tool.
Love the nomad lifestyle but not sure how to pull it off? You’re in luck! In this episode, the panelists discuss their personal experiences working (and sometimes living) remote. They cover how to generate leads and book clients consistently, why the “multiplier effect” is HUGE for making your new ideas lucrative, and the ONE reason you don’t need revolutionary ideas to find success.
We’ve been hearing about blockchain and Web3 for years now, but its heyday is sooner than you think. In this episode, Will and Jonathan discuss why NOW is the time to dig into blockchain, how those in Dev Ops can approach these new technologies (and not get overwhelmed), and what Jonathan learned from a, well, “crazy” interview.
Jonathan talks about how he prepares for a tech interview, and offers insights from the point of view of a hiring manager as well.
Jillian, Jonathan, Shimon, Will, and Chuck discuss the history of the show, their favorite episodes, and what they think is coming in 2022.
Daniele Fontani joins the Adventure to discuss the different kinds of Ops like NoOps, AppOps, etc. He makes fun of the different ways that people try to extend DevOps into other types of movements and why the different focuses may or may not be appropriate ways to manage resources.
Will and Jonathan have a conversation about whether or not you can use Scrum with DevOps. They also discuss different alternatives to Scrum and how you can use them instead of Scrum or whether Scrum is the best fit.
The Adventures in DevOps crew discuss the various certificates that exist and which ones you may or may not want to consider getting. They talk about whether you need one in the first place and the value that different markets place on the certificates.
Mani provides us with strategies and tactics to get Deep Work time and how to get our minds into that focused state for hours at a time. He has read hundreds of books that have taught him the secrets to getting more done by getting into this state.
Jillian, Jonathan, Will, and Chuck discuss where the line is between Development and DevOps and what the difference is. They also get into the value of each and when crossover is likely to occur.
The panel puts their heads together to talk about how to bring DevOps practices into a work situation based where they're not implemented. They discuss the various pro's and con's of specific practices and how to get people on board with adoption.
The panel jumps in and discusses the Minimum Viable Continuous Deployment from the manifesto on the web and discuss where they agree and disagree with the requirements listed there and clarify some of the ideas in the document.
Abhinav Dhasmana joins the adventure to discuss how he got Kafka to scale to handle thousands of messages. He explains how to scale Kafka up and how to allow applications to scale with the messaging architecture provided by Kafka.
Will and Jonathan jump in this week to discuss how to get started with a career in DevOps and how companies can get things started at your company with DevOps. They discuss the pitfalls of outsourcing your devops and how DevOps should be working within your application space and within your organization.
Henry Been and Erwin Staal join the adventure to discuss Microsoft's options for defining infrastructure as code on Microsoft's Azure cloud offerings. They walk the panel through setting up ARM templates and using the Bicep language to specify how your infrastructure gets set up , run, and managed.
Alex Feiszli from GRAVITL joins the adventure to discuss how to securely connect Kubernetes clusters across clouds from one cluster to another. The discussion spans how to make secure connections and how the connections might be used.
Troy Dreier joins the adventure to discuss Manning's LiveProjects platform where developers can work through exercises and learn the things they need to just-in-time. Andres Sacco is one of the authors on LivePlatform and joins the adventure to discuss cloud optimization and his experience building a LiveProject showing people how to optimize their cloud setup.
Will Kelly is a technical writer who joins the adventure to discuss bridging the gap between open source, development, and DevOps. He explains the personal and technical skills needed to help folks understand the need for using Open Source software and how developers and DevOps practitioners can communicate about the security concerns around complimentary practices of the two groups with the realms of their jobs.
The Adventures in DevOps panel take over and discuss whether or not DevOps Engineers need to know how to code. The panel offers their perspectives on the pros and cons of knowing how to code and the limitations placed on DevOps Engineers who don't know how to code and the tradeoffs of spending time on code versus other skills that can pay off for your customers.