It's Not a New Ballmer Microsoft Needs; It's a New Gates
theodp writes "Over at GeekWire, Todd Bishop posits that Microsoft doesn't need to replace Steve Ballmer as much as it needs to replace Bill Gates. 'The perennial push to oust Ballmer is back,' Bishop says. 'But as long as we're all going down this path again, there's actually a larger issue to address: Microsoft no longer has an overarching technology leader next to the CEO at the top of the company – someone with a strong engineering background and technical vision, surveying the field and calling the plays. There will never be another Bill Gates. But there should be someone in his former role as chief software architect, if not in title, then at least in effect.' Ray Ozzie was supposed to be The One, but for some reason that never really worked out (Dave Winer warns BigCo politics can crush even the most innovative). Any thoughts on who might 'fill the bill'?"
I wonder what would happen to Microsoft's share price if Gates himself stepped back into the role?
Science is all about firing a drunk pig out of a cannon just to see what happens.
What Microsoft needs is someone who understands what an Operating System is and what it is not. A genuine geek who understands that a 40 GB operating system is wasteful and unnecessary and a sign of incompetence and stupidity. Someone who understands that when your software grows to 10 times the size of your competitors (Linux and OSX) something is badly wrong and needs to be fixed. When you don't know the first thing about coding you have no business managing coders. It will all just turn into one giant predictable mess. As we have seen with post-Gates Microsoft.
Quite an experience to live in fear, isn't it? That's what it is to be a slave.