
Sign up to save your podcasts
Or


Take a listen to the first version of our thoughts on revision control.
In this episode, we discuss revision control. Revision control is a topic that is near and dear to both Chris and I and we’ve got some strong opinions on how it should be used.
(SPOILER ALERT: For lots of things!)
We cover what revision control is, why it matters, and what should be revision controlled. We also talk a bit about how to deal with secrets or sensitive data that may need to pass through revision control.
We go on a bit of a tangent on why tooling that generates artifacts that can be revision controlled are preferable to tooling that is just “magic”. That discussion is thanks to Chris digging up this article on declarative configuration management versus VM templates.
Stay tuned for our next show on Time Management, with our first guest!
Now that the holidays are over, here are some thoughts Chris and I have on them.
In this episode, we talk about the holidays, specifically how they impact operations personnel. We cover on-call considerations, bonding with family and co-workers over alcohol holiday parties, and code freezes.
Hope you all had a great holiday season and have had a great start to 2014!
In this episode we talk about documentation. Really taking a big picture view of how to document things and what should be documented. Along with that we try to talk a bit about the types of documentation that are not necessarily obvious, like monitoring.
During the show, Steve mentioned the Stack Exchange data center move. If you are interested, here are some pictures and commentary: http://www.reddit.com/r/cableporn/comments/1bcxfi/a_few_photos_from_the_stack_overflow_data_center/
Hope you enjoy the show.
This episode is really focuses on how Ops adds value and discusses lots of aspects around the roles of traditional IT and WebOps.
This episode provides an introduction into the goals of the podcast and a little bit of info about Chris and Steve.
We skipped the news section this episode but will pick it up in the future.
From the publisher's feed