I’m writing this post to make sure our if this then that recipe is working. It also seemed like a fun time to try out the Liquid Tweet Tag for Jekyll and Octopress that I just put into the code.
Nifty, huh?
]]>Or you can just listen!
We’ll be (hopefully) recording our first podcast on Thursday. Which is two days from now. We need a tagline by then, just to help people understand what we are about. And as much as I love the name and the riff on Arrested Development, I don’t want to use that in the tagline.
Fundamentally, our goal is to be accessible, friendly to people new to the concepts, and very devoid of “inside baseball”. And also to not make people feel dirty for using Microsoft products. Any ideas for a great tagline? Please either tweet use at @arresteddevops or leave your thoughts in the comments.
]]>But how did this happen? I’m a big fan of a few great DevOps type podcasts, most notably the following:
With so much great content out there, why do we need another one? One thing that came to mind is that, for better or for worse, these podcasts have a very heavy FOSS focus to them. Which is fine, because FOSS is pretty cool. But there’s a lot of Windows out there in the real world as well. It seemed that there were more voices to be heard. Which basically maeans that I want you to hear my voice.
I’ve had this domain for a bit, and always intended to create a blog here. However, a podcast seemed like a cool idea. Especially since I’ve never done one before. But I wasn’t about to do one myself. Because, well, I’m kind of lazy. Also, I’m the “Ops” in “DevOps”, and that makes for a one-sided conversation.
I met Trevor at the Downtown Chicago Azure Meet-Up back in October, and he presented about Continuous Integration at the next month’s meetup. Of course, I completely steamrolled everything he had to say, which is why I immediately thought of him as someone to do a podcast with.
We don’t know what this will be yet. Watch this space for updates. I don’t expect that your professional life will change or your organization will achieve amazing levels of productivity just based on anything we say, but hopefully you’ll enjoy it once we have something.
One thing I can guarantee: Lots of Doctor Who references.
What would you like to hear on a DevOps podcast? Thoughts on this in general? Let us know in the comments!
]]>