How do we know, we know what DevOps is? For episode 46, we sit down with Praxisflow’s Kevin Behr (whom you might recognize as one of the authors of the Phoenix Project) and Jabe Bloom to talk about these and other heady questions, including: what can we learn from the Agile community? Where is DevOps headed in the next five years? Who is Frederick Taylor and what does he have to do with DevOps? And what do English coal miners from the 1940s have to do with DevOps? Find out the answers to these and more as we discuss:
When most of us think of where the gravitational pull is in DevOps, places like San Francisco, New York, and Belgium spring to mind. But the Midwest? You bet, pardner! For episode 45, we take a field trip to Minneapolis for its first ever DevOps Days. With a panel of organizers and speakers from the event (including Patrick Debois!), we discuss the various talks as well as the open spaces and evening events, examining how DevOps in the Midwest is alive and well and has something to share with us all! Join us for a panel discussion on what it’s like doing
DevOps on the Silicon Prairie
Join J. Paul Reed, aka @SoberBuildEng, EJ Ciramella, aka @eciramella Seth Thomas, aka @cheeseplus, Pete Cheslock , aka @petecheslock for the discussion, plus a the last couple of weeks in News & Views and the triumphant return of DevOps Dear Abby!
For episode 44, we sit down with Lanette Creamer, a proponent of context-driven and agile QA practices to discuss what “quality” means in a world moving toward DevOps practices. Lanette started in QA back when solving “the blank screen” involved “typing in win.exe” and has been testing everything from publishing to medical records software. We figure out what it’s like to be a QA engineer in this changing environment and how we can all help produce better quality in the software we work on. Join us as Lanette guides the panel through:
As tech companies implement all sorts of ways to increase their output, the often-undiscussed tradeoff is how it impacts employees. Most tech workers have struggled with burnout in a role, at a company, or even in the area of tech they’ve focused their career; some of us have even suffered through burnout without noticing it: we only became aware when friends and family intervened to let us know how off-the-rails our work/life balance had become. In episode 43, we take a look at the signs, symptoms, causes, and strategies for:
Join J. Paul Reed, aka @SoberBuildEng, Youssuf El-Kalay, aka @buildscientist, Sascha Bates, aka @sascha_d and Pete Chesslock, aka @petecheslock for the panel discussion, plus a the last couple of weeks in News & Views and some opinionated thoughts and feels!
For episode 42, listeners might be hoping that we’d delve into the meaning of life, the universe, and everything… and if your universe consists of deploying and managing applications on Windows, that’s exactly what we’ll be doing! The panel sits down with Steven Murawski, site reliability engineer with the venerable Stack Exchange and Microsoft community MVP to discuss the goings on at Tech Ed last week, Microsoft’s recent open source offerings, new Azure features that are facing down Amazon, and with DSC and Server Core, why it seems Microsoft is really changing the way they develop their server products. Join us as we explore:
Member of an underrepresented group in the tech community? Tell us why you’d like to go to Velocity Santa Clara this June 25th and 26th; send us an email at email@example.com by May 28th, 11:59 pm PDT and we’ll try to help you get there!
In our first ever contest, we also have a Velocity Santa Clara ticket we’ll be giving away; take a picture yourself in the weirdest place you listen to The Ship Show, post it to Twitter, and tag it with the #ListeningToTheShipShow hashtag! Entries for that need to be tweeted by May 31st, 11:59 pm PDT.
11:00 – Main Segment: The State of DevOps Life in the Windows World
Bring up the topic of tech industry recruiting with any developer and you’re likely to get an ear-full: stories of recruiters treating candidates disrespectful, clueless recruiters who don’t know any of the acronyms, recruiters continuing to talk to you even after you’ve asked them to stop… the list goes on and on. In fact, it’s so prevalent, Twitter and Tumblr accounts have popped up just to make fun of recruiters. But why is recruiting so broken in our industry? Are all recruiters like that? And is there anything all of us—companies, recruiters, and candidates—can do to make the experience a bit better (and more efficient!) for everyone? Join us as we put recruiter Sam Whooley through the gauntlet for:
Your Profile Tells Me You’re Perfect for this Amazing Podcast Opportunity
Join J. Paul Reed, aka @SoberBuildEng, EJ Ciramella, aka @eciramella, and Sascha Bates, aka @sascha_d for the discussion, plus a the last couple of weeks in News & Views and a new tool tip!
Member of an underrepresented group in the tech community? Tell us why you’d like to go to Velocity Santa Clara this June 25th and 26th; send us an email at firstname.lastname@example.org and we’ll try to help you get there!
11:12 – Your Profile Tells Me You’re Perfect for this Amazing Podcast Opportunity
It’s time again for all the Chefs to get together in the kitchen in San Francisco and look at all of the developments in the last year, plus look forward to the next year in the configuration management space, industry trends in DevOps and, of course, Chef! We grab a bottle of bourbon, some bacon, and sit down to discuss all of the “shenanigans” at ChefConf 2014, as well as look back at the keynotes, our favorite talks, hallway track conversations with old friends and new, plus reveal this year’s Awesome Community Chefs. Join the panel, plus a couple of very special surprise guests, as we go:
Creating that initial environment for your application to run in is a solved problem. Or is it? On the market today, there are a seemingly ever-increasing number of tools to facilitate that process: CFEngine, Puppet, Chef, Vagrant, Packer, Ansible, Salt Stack, Rundeck… the list goes on. In episode 39, the panel takes a closer look at one of these new tools: Docker. The panel is joined once again by Atlassian’s James Dumay, since the discussion was prompted by a question he tweeted: “[S]omeone thinks Docker can replace Chef/Puppet. I believe they are at least complementary.” Are they? And what workflows make sense for Docker? Join the panel as we try:
At some point in every discussion of DevOps or organizational transformations, The Phoenix Project, the seminal book by Kevin Behr, Gene Kim, and George Spafford comes up. More than just “A Novel About IT, DevOps, and Helping Your Business Win,” it’s become a “water cooler” book for everyone from sysadmins in the basement to CxOs in the boardroom. Released in January 2013, we sit down with Gene Kim to look at how The Phoenix Project has influenced our industry over the past year, plus ask Gene questions we’ve always had about the characters and the story. Plus, we find out what Gene’s been working on since Phoenix shipped. Join us for:
A Year of The Phoenix Project with Gene Kim
Join J. Paul Reed, aka @SoberBuildEng, and Sascha Bates, aka @sascha_d for the discussion, plus a the last couple of weeks in News & Views and a review!
Our topic for Episode 37 was originally on scaling self-service of configuration management (the source code kind, not the infrastructure kind!) good practices, but quickly morphed into a discussion of what organizations need to pay attention and foster to support their tools teams in their often-cited mission of creating a self-service culture and self-service infrastructure. Paul and Sascha square off over the notions of traditional “service” teams and the newer notion of integrated “tools” (“DevOps?”) teams. We also touch on warning signs for automating self-service processes, including in the CM space, really examining how and why you convert which processes into self-service, ways to get teams to buy into your self-service initiatives, and what’s in the best interests of the entire system that is your software development organization. Join us as we discuss the finer points of: