ConceptJunkie's Journal: Microsoft Rules

I like Microsoft rule #3 so much I hate to change my sig to #4.

These are certainly not real rules, but are rules that Microsoft appears to follow by their actions.

Here are the others I've come up with:

Microsoft Rule #1: Every app must be expanded until it can be used as a vehicle for a virus that can trash the system. (In fact, no app is useful _unless_ it can be used as a virus vehicle. If MS wrote edlin today it would have scripting that could be used to access kernel functions via TCP/IP.)

Microsoft Rule #2: Flexibility in UI is acceptable, but defaults must confuse new users and frustrate experienced ones.

Microsoft Rule #3: GUI standards are no longer necessary. Shiny objects are always user-friendly.

Microsoft Rule #4: No useful thing can be designed unless by committee. Consistency and clarity are not signs of maturity. Simplicity is for amateurs. (Breaking up Microsoft would have about as much effect as asking a blind guy if he would not look over people's shoulders during the final exam.)

Microsoft Rule #5: Security has less "gee-whiz" factor than skinning and is therefore a less important feature. (Plus it's just too darn much trouble to check each memory buffer copy, especially when we'd rather spend time making the media player look like eyeballs.)

Microsoft Rule #6: Dominating a market is the same as excelling in a market ("Economic might makes right", or more simply "A monopoly means God smiles on everything you do.").

Microsoft Rule #7: Change is improvement by definition. (But this is universal among software companies...)