Too Good to be True

I was very excited for a few minutes. But then I realized that I had parsed the sentence incorrectly. Bad Captain! Bad, bad Captain. *sigh*

Oh, what was I excited about? Well, Tuxedo Guy (aka Bob Balaban) posted this morning about his schedule for Collaboration University. And one of the things on his agenda is:

I'm sort of co-hosting a closing session with Mary Beth on the future of Notes and of Notes/Domino programmability.

My first scan through that post had me thinking that IBM had decided to turn Mary Beth Raven loose on the design tools as well as the end-user experience. And I was practically chair dancing over the idea. But then I realized I was being a bonehead (no comments from the Peanut Gallery, mmmkay?). Mary Beth will be focused on the future of Notes, Bob will focus on the future of Notes/Domino programmability. And the stuff Bob's working on is critical, make no mistake about it, so don't think that isn't cool. But I've been wishing for more focus on the usability of the tools available to developers for a while (in so many words, I said recently: "Where's the Mary Beth Raven for developer tools?"), and I thought I was about to get my wish. In spades. 

Oh, well. There's still hope, because we - obviously - haven't seen the tooling catch up with the client yet. But I'm becoming more and more convinced that the tools IBM gives us developers all suffer from "designed by an engineer" syndrome. They can be very powerful, but they are rarely very usable. We all know that Visual Studio kicks Domino Designer's butt on usability. And it kicks Eclipse's butt, too. 

Oops, there I go again, not playing nice with the other children. I wonder if the number of Lotus Geeks who will still speak to me has fallen to single digits yet?