Change in Longitude
By stern on Jun 03, 2006
I tend to mark time relative to events rather than calendar dates. The Miracle on Ice happened on a Friday night at the midpoint of the 1980 Winter Olympics. My summer's tenor is pitched on the 4th Monday of May, when Memorial Day is observed at golf courses and beaches. And for the past 22 years, I can recall what I've done on the Friday before Princeton Reunions: it's sort of a half-New Year's Eve for reflection. I've spent it in Connecticut, China and Cincinatti, and a dozen other places that break my alliteration.
Seventeen years ago, the Friday before Reunions, I accepted a job offer from Sun Microsystems to be a systems engineer in the Boston area sales office. I was fleeing a startup company in the molecular modeling space that was attempting to port industry-leading visualization software from Sun workstations and SunOS to a combination of MS-DOS and VAX/VMS. The exit criteria were pretty obvious. By the time my wife and I arrived on the Princeton campus, my Tiger classmates were questioning why I was joining a company that had just pre-announced a quarterly loss (that was, I believe, the last time Sun went cash flow negative for the fiscal year).
My answers were simple: the technology was solid, the people were smart, and the combination was fun. We've come a long way since SunOS 4.0.3 and the SPARCStation 1, but those traits remain constant.
On Friday, I changed longitudes in Sun's organization chart, the Friday before Reunions, the first Friday of the Jersey summer, and one that I hope I remember for another 22 years. I'm returning to Sun's field organization to be the spiritual and functional leader of Sun's global customer engineering force. Defining the exact organizational parameters is this week's job, and it will include both structuring our systems engineering community as well technical leadership for the entire customer-facing engineering community at Sun.
Here's what I do know:
With our software strategies in full bloom, from dynamic languages on the Java Platform, to open sourcing the stack, to building a new value proposition with Aduva, it seems a rather strange time to leave my role as Software CTO. There's never a good time to make a job change when things are going well; but I believe you have mentally made the change when you find your inter-email thoughts turning into "How cool would it be if..." propositions about the new role.
In short, that's why I'm back in the field: because (a) we have great technology, (b) there are amazingly smart people to turn that technology into systems, and a management chain that wants (a) times (b) to equal fun. Again. In the words of Stuart Scott, it's time to rock the party that rocks the (engineering) pinata.