Billg the Manager (2021)
Key topics
Diving into the multifaceted legacy of Bill Gates as a manager, commenters dissect his innovative contributions and leadership style, with some arguing that his effectiveness as a CEO shouldn't be conflated with moral "goodness." A lively debate ensues, with perspectives ranging from the notion that being a "bad guy" is necessary in the business jungle [ferguess_k] to the observation that great problem solvers like Gates can be disconnected from the struggles of others [9rx]. As the discussion unfolds, it reveals that Gates' complexities – from his role in Microsoft's browser wars to his later philanthropic endeavors – continue to fascinate and provoke reflection on what makes a truly effective leader.
Snapshot generated from the HN discussion
Discussion Activity
Active discussionFirst comment
1h
Peak period
11
2-4h
Avg / period
3.3
Based on 30 loaded comments
Key moments
- 01Story posted
Jan 7, 2026 at 11:18 AM EST
2d ago
Step 01 - 02First comment
Jan 7, 2026 at 12:39 PM EST
1h after posting
Step 02 - 03Peak activity
11 comments in 2-4h
Hottest window of the conversation
Step 03 - 04Latest activity
Jan 8, 2026 at 12:28 PM EST
1d ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
I've always held the belief that even though Gates may have been an effective manager, he was a terrible person. IMHO, his repeated anti-competitive, deceptive, and often illegal behavior was the main reason for Microsoft's success.
https://www.folklore.org/MacBasic.html
An interesting spin on a "real" BillG review:
https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev...
Microsoft made many mistakes, but I don't see how integrating a browser into Windows was one. I still can't fathom that we live in a world where that got Microsoft in such trouble, but acquiring Activision Blizzard was deemed ok.
As for legality, I'm not a lawyer and definitely not an antitrust one, but as I see it, an OS is almost by definition an amorphous collection of tools that users need to make proper use of their computer and nowadays I can't imagine an OS that doesn't come with a browser, so would argue that they were absolutely right in integrating it. If anything, I see much more merit in suing them for abusing their OS monopoly to go into the solitaire gaming space.
I remember paying for Netscape 4, and I remember the pile of steaming garbage I got when I did that.
The ethical issue would be around making it technically harder for competitors to create a web browser. Eg, standard practice on mobile phones (which is worse than anything MS ever did and has always seemed fine to me).
One of my favorite places to go in the world is jungles. I've never really encountered bad guys there, and I've never fought anyone I've met in a jungle. I think you might want to work on a better allegory, and also question your assumptions about any of this since on this I can't agree literally or metaphorically.
The trouble with great problem solvers is that they assume everyone else is also great at solving problems, and thus understand that if they are causing trouble for other people that those other people will step in and solve the problem that was created.
But, as you point out, not everyone is a problem solver.
They started the company. They were parents.
He may have enabled scalability by being more hands off, but I'm still kind of surprised it took him that long to learn that software quality had fallen off that far. And I'm not even getting into the monopoly aspect of it. Maybe that was the business model all along, you can save costs by not adhering to quality standards as long as you land the right exclusivity deals with OEMs. Microsoft gonna Microsoft.
A great example is how Apple used to be great at this. These days.the.keyboard.is.practically.unusable. As in it still doesn't type out the letter you tapped and you can see this via slow motion video recording https://www.youtube.com/watch?v=hksVvXONrIo
It's not at all wrong to call out subordinates in the company for quality feel. It may seem like it leads to misprioritization (everyone in the company scrambles to fix the issue you saw) but not doing this at all is far far worse. Look at this issue BillG raised and the fact that no one cared until it was raised. Big companies are very siloed by nature. The only thing that breaks these silos is the leadership doing things like this.
What did he used before ? UNIX ?
Isn't that to some extent (or perhaps exactly) what is going on today? All employees at MS are using the polished Enterprise edition without all the cruft and without many of the annoyances. I bet most of them have never tried to use, eg, the home edition. Few of them has probably ever tried to pick a new PC from a retail store full of trialware and "optimizations" made by the retail store.
The point is that most MS employees don't get to see the edition of Windows that we, normal consumers, do.
It was 2003, and Microsoft's next version of Windows, codenamed Longhorn, was not doing well. On top of that, Google and the rest of the internet natives were eating Microsoft's lunch, and many analysts expected the company to fade away, as IBM had done before.
Bill Gates, obviously, didn't want that to happen, and true to his nature, was looking for a technological solution. In many ways, Longhorn was fighting the last war: it invented a new graphical subsystem and a new storage system, at a time when modern apps were happily using HTML and SQL. Groove Networks had developed a peer-to-peer synchronization technology that blended online and offline so an app could have the best of both worlds. It was a true local-first architecture that was also internet native.
Gates arrived early in the morning with one or two assistants. In 2003 he was still the wealthiest person on the planet, but he carried himself like any normal engineer. One of my colleagues, who hadn't been told he was coming, only learned about it because they rode with him in the elevator. He introduced himself and made small talk. You can imagine their shock.
At the meeting, we presented our technology and our ideas for how we could fit into Microsoft's plans. Later I learned that this was a mini-product review, like Sinofsky talks about in the OP. I pitched him (somewhat half-baked) ideas about how Windows files folders could become collaborative, shared folders. He was very engaged, but thankfully polite--he didn't tell me it was "the stupidest thing he had ever heard." I suspect he was on his best behavior because he had already made up his mind to buy the company.
The highlight of the meeting, for me, was watching him and Ray (whom he'd known for a while) riff on everything around Windows, the internet, and technology in general. It was like improv, where every idea someone came up with was followed up with, "Yes, and then you can also...". You could tell Gates was engaged because he kept rocking in his chair, a classic tell we later learned.
Microsoft did ultimately buy Groove Networks, but not for the technology. I realized much later that Gates had bought Groove mostly to hire Ray. In 2006, Gates announced that he was retiring and appointing Ray Ozzie as Chief Software Architect.
At Microsoft, Ray spearheaded a project codenamed Red Dog, which the marketing folks later called "Azure". I'm convinced that Ray doesn't get enough credit for his contributions to turning Microsoft around.
Had Bill already planned all this when he visited us in 2003? Probably not, but seeing his mind work, it wouldn't surprise me if he had a little bit of an inkling. You never know.
Ray has always sounded visionary to me. His comments on HN have been enjoyable to read, too: https://news.ycombinator.com/user?id=rozzie
https://www.nytimes.com/1990/03/20/business/business-people-...
But less than two years later
https://www.nytimes.com/1992/02/04/business/microsoft-presid...