First off, apologies for the serialization error. We know, the last show was #212 in the title but #211 on the filename, when it should have been #211 through and through. We get it, and we’re very sorry, especially to you OCD folks who are twitching uncontrollably right now. Don’t fire us. Why didn’t we make this show #213 and just skip #211 altogether? Because we have a production schedule that’s planned several weeks in advance. Changing this one to #213 would mean that #213 would become #214, and so on for several weeks of lunacy and confusion. And probably crying. Yes, most definitely some crying involved.
On a related note, Packet Pushers is poking at the idea of hiring a webmaster / content manager sort of person that would help us avoid these sorts of challenges. Let us know if you’re interested in an exploratory conversation. Yes, seriously.
Back to the podcast. So, changing numbers is actually sort of hard. Almost as hard as SDN, it would seem. In this show, Greg and Ethan discuss just how hard it is for both vendors and practitioners to get behind any one particular SDN strategy, in part because there’s just so many different strategies out there. Has SDN become all about corner cases instead of transformative technology? Hmm.
We talk about other things, too, such as whether or not IT people should get fired for making mistakes that cause an outage. Think about that, fellow engineers. Fat finger an interface ID. Cause an outage. Pack up and go home.
And finally, Greg and Ethan have a bit of fun with a segment we’ve titled “Consultobabble.” We hope it elicits at least a giggle. We certainly had fun recording the bit, so we’ll do more unless you just hated it. In which case, we won’t. Because we’re all about you.
Last but not least, please swing by our sponsors for this show, Auvik Networks and NetRounds. We appreciate them sponsoring Packet Pushers, and we hope you do, too.
