Starting Monday, I'll be working again, joining Comcast as SVP and Chief Software Architect.
The first thing I said when talking to people at Comcast (early on) was "Comcast? Software? Isn't that an oxymoron?" Suffice it to say, today they're a Cable Company... but tomorrow?
Well... more information in future posts... but mostly I was motivated, at a personal level, by three (professional) considerations:
(a) At this point in my career, I wanted to either go do my own thing again (my usual default stance), or take a significant role at a significant organization; Comcast did $26B in revenue last year, and, though still facing far more demand than supply in the market place is still aggressively pursuing a deep business transformation for the new millennium. They're in a great place, and they're running very fast.
(b) I'm gratified that my particular skills and experience will be applicable and valuable, but also wanted to play in areas of complexity where I had little experience (Cable/Telecom) - nothing beats tackling new problems. And Comcast has no shortage of that, though they have a strong market position.
(c) I was quite impressed by the caliber, intellect, and alignment of the executive team. That last, in particular, I've found to be uncommon in large organizations (not just from my AOL experiences, but the half dozen or so "usual suspects" I've spoken to over the last few months).
Updated my LinkedIn profile last week - and am currently drowning in paperwork (employee stuff, moving, buying, schooling, re-locationg, eeeerkkk...) - but its all good :) In particular, my wife grew up in Philly (where Comcast Corp is headquartered), and it was while working near there that we met, so geography is actually a big part of the appeal, too - we have lots of friends and family in the area.