Slashdot Mirror
Bill Gates' Management Style
replicant108 wrote in to give us Tom Evslin's fascinating account of working for Microsoft in the early 90s. "So you're in there presenting your product plan to billg, steveb, and mikemap. Billg typically has his eyes closed and he's rocking back and forth. He could be asleep; he could be thinking about something else; he could be listening intently to everything you're saying. The trouble is all are possible and you don't know which. Obviously, you have to present as if he were listening intently even though you know he isn't looking at the PowerPoint slides you spent so much time on.
At some point in your presentation billg will say "that's the dumbest fucking idea I've heard since I've been at Microsoft." He looks like he means it. However, since you knew he was going to say this, you can't really let it faze you. Moreover, you can't afford to look fazed; remember: he's a bully."
Maybe you should've spent less time on the PowerPoint slides and more time thinking about how your idea was going to (figuratively) grab Billg around the throat and shake him until he said, "That's the best idea I've ever heard since I've been here at Microsoft."
I mean, shit, do you really think you're going to impress the CEO of Microsoft with a PowerPoint presentation, of all things?
!#@%*)anks for hanging up the phone, dear.
After a State Dept. staffer turned in their first report to the big boss, it would frequently come back with a scrawled note indicating it was totally unacceptable, slipshod work, etc. The staffer would go back and spend the next couple weeks furiously researching and revising before submitting a completely rewritten draft. Back would come the comment that it was "not good enough -- should be much more thorough". After another three weeks of research, the staffer would add a cover letter to the latest rewrite begging the boss to specify where the report fell short, since the staffer had now spent practically all of their waking hours over the past two months working on it, etc.
"In that case", Kissinger would say, "I'll read it".
Reminded me of Joel on Software's first BillG review and how he handled it.
Bill Gates' dad is a lawyer. He came from a family where "cross-examination" in a legal sense probably went on from time to time (i.e. questioning a hostile witness). It sounds like he was inculcated with the culture.
Also, when dealing with judges, particularly when the witnesses or jury are out of the room, lawyers can face something that can be pretty similar to what was described here. So, ok, it's hard on the computer scientists, but welcome to what lawyers get to deal with all the time. It's an accepted practice.
Long and short of it--make sure your thinking is done BEFORE you present. Otherwise, as is to be expected, you're toast, whether the "toasting" is done by the CEO or a judge.
True enough. Though if you found this article interesting, you should try reading Barbarians Led by Bill Gates. It's an insider's perspective on the going-ons inside of Microsoft in the early days. It's especially freaky to learn that they started coding much of Windows in BASIC. (Which I suppose comes as no surprise given that the Microsoft of the time was known as "the BASIC company".) Just like in this article, Gates was described as the King of the Hill with whom very few of the developers wanted to tangle.
:-P
A particularly amusing anecdote was when the author was working on a clock application for Windows. He found the BASIC flood-fill routine to be buggy and quite poor, and set about to rewrite it. He then headed for Gates' office to tell him that he wanted to replace the existing flood-fill routine "because it was crap". (Or something to that effect.) Some of his coworkers tried to warn him off, but he headed straight in and showed off his work to Gates. After forcefully championing his work to Gates, Gates agreed to allow the fix. As he came out of Gates' office beaming, one of the coworkers said to him, "You know who wrote the original flood-fill routine, don't you?"
Yep, it was Gates. And the author had just told him that his code was crap to his face. Doh!
Javascript + Nintendo DSi = DSiCade
This parable illustrates how personal defects get in the way of quality. If the code is crap, the code is crap, no matter who wrote it. If politics or sensitive egos block improvements, quality suffers. Compare EgolessProgramming.
This "my code is perfect" attitude is alive and well. A friend of mine started a new job recently and found that his boss:
you had me at #!