Today was my boss’s last day, and, ironically, my first anniversary. Julian Lombardi will be Duke’s Assistant Vice President for Academic Services and Technology Support. He’ll be responsible for the university’s IT customer service and development.
They made him an offer he couldn’t refuse.
This youngest of the Ivy League has established a reputation with such programs as their initiative to give each student an iPod. They’re very excited about Croquet, and seek to establish a non-profit there to coordinate activity between the growing list of institutions working on and with this technology.
It will be some time, at least a year, before the Duke Office of IT can actually do Croquet technical development. Regardless, Julian will continue to collaborate with us on papers and our work on user interfaces. We’ve had some terrific fights on architecture, as can only happen between people comfortable with themselves and with each other. I expect this to continue by phone and following release 1, within Croquet itself.
Our team here in Wisconsin remains unchanged. With our colleagues in Minnesota, we continue to work on the Croquet core and frameworks, integration with campus enterprise systems, and applications for teaching and learning. My title of Lead Croquet Developer remains unchanged, but I now take on the leadership of the project here. UW-Madison’s Division of Information Technology is a fantastically talented and eagerly helpful organization, but there is a great challenge as well. DoIT’ has 700 employees, a $70M budget, and more than 55,000 sophisticated users. There are a lot of ins and outs. Did I mention that in Julian’s previous career as a research biologist, his job had been to literally swim with sharks in the wild? Given the machinations at HP, I’ve appreciated Julian’s observation of the local ecosystem.
However, I think Julian’s greatest talent has been to convey to people the fantastic breadth, complexity, and possibilities of Croquet. Check out this presentation: in Flash, or Mediasite. For any product, it is incredibly difficult to grasp the technical concepts correctly and convert these into meaningful possibilities. It’s even harder to simultaneously listen to the market and customers in a true two-way conversation, and incorporate the results into the core technology itself. It’s not about chasing after features or adding stuff. It’s about removing the useless “cool stuff” that nerds think of, until not only the users, but the nerds themselves can think in terms of an architecture that naturally follows the user’s goals for the system. This is rarely done right in normal stuff, but when inventing the future….? No one does it better than Julian. His new position is a great forum to continue doing this internationally across institutions. But I love Julian enough to be really pissed that he’s not going to be doing that on campus here at Wisconsin.