Slashdot Mirror
Ray Ozzie Quit... What Took Him So Long?
GMGruman writes "The mainstream press acts surprised that Microsoft's chief software architect is resigning, but InfoWorld's Woody Leonhard explains through a review of Ozzie's efforts at Microsoft how the Redmond giant has consistently ignored and squandered the design savvy that Ozzie has tried to bring to the table. If you ever wondered why Microsoft's products like Windows and Office are so bloated and underwhelming, while Apple's are almost always wonderful experiences, this analysis will solve that mystery. And you too will wonder how Ozzie could have lasted so long at a company that doesn't believe in design."
If you ever wondered why Microsoft's products like Windows and Office are so bloated and underwhelming, while Apple's are almost always wonderful experiences, this analysis will solve that mystery.
No bias here..
If you ever wondered why Microsoft's products like Windows and Office are so bloated and underwhelming, while Apple's are almost always wonderful experiences, this analysis will solve that mystery.
Finally the mystery has been solved! The suspense was killing me.
Seriously, this is the man behind Lotus notes and Groove. Two of the biggest piles of snot ever made. His existence at MS was a blight. Now if they can get Balmer to join him they may have something there.
When I was there, Microsoft graded every project on a curve, with compensation in the balance. The "lowest" performers got slammed, the peak performs got rich. I imagine nothing has changed, except fewer people get rich.
Their system of evaluating and compensating developers rewards "hot dogs", who by any standard are good developers, but penalizes cooperation and useful developer documentation. Anything you might do to help someone on your team be successful automatically and in a very measured way hurts your own compensation. Few developers can rise above this and work with others outside of what is necessary to get the appropriate check marks on the review. And when individuals do work closely with each other, they are very selective as to who they work with. You can't afford to make *everyone* on your team successful. Remember, the bell curve WILL be applied.
Other mechanisms are used at Microsoft are very good. They have a huge commitment to testing, and a huge commitment to process. They know within a few months into a project when they are going to deliver. They know well in advance when projects are going to be late. They research and know the competition.
However, at the end of the day, their culture does not allow for clean design. Clean design means working together and making it a priority to make all developers on a team as productive as possible. But even if the differences between developers are tiny, the bell curve will be applied. People will win, and people will lose. And don't think for a moment that subjective decisions do not come into play based on a developer's reputation and ties with other developers.
In the end, if you don't know how something works, don't expect the comments to be useful. Don't be surprised if two interfaces sit next to each other and both do nearly the same thing. Obviously one developer implemented something, and the next couldn't figure out how to use it.
Microsoft's bloat is mostly a result of their development culture. Sure, supporting ten years of file formats is a factor, but not as important as their development culture, IMHO.