I actually wrote this several months ago, before I started this blog. Two (really three) great but very different blogs posted this week made me decide to dig it up.
I took some C classes in my early 20’s.
It was mostly for the exposure. I had absolutely no call for anything of the kind in my job at the time, nor any plans to significantly alter my career path. And yet, they’re some of the classes that have stuck with me the most over the years.
Until then, my sole coding experience had been short BASIC programs to create silly graphics with quarter-inch color blocks on Apple IIes in elementary school. This was different.
There were a pair of stories in the trades last week in which VMware finally took off the gloves and effectively proclaimed themselves the antithesis of Cisco in their approach to—well, not SDN, since both companies say they have gone beyond it. But to the next generation of networking, in any case.
(That’s rather a mouthful, though, so for the rest of this post I’ll refer to their efforts as SDN just as the rest of the industry does; please forgive the shorthand. I’ll get back to the other current discussion about whether SDN 1.0 is dead in another post.)
Any good journalist knows that a good controversy attracts eyeballs, and the best controversy has two—and only two—diametrically opposed antagonists. More than two would complicate the storyline. So we got stories that suggested not only that VMware is now officially at odds with Cisco, but also that SDN architectural options are themselves both binary and comprehensively represented by Cisco and VMware.