3 ms·

"Microsoft doesn't know how to..." is an unfounded disparagement. Microsoft definitely knows how to write software, okay? They're really good at it. They ship

by kabdib 11y ago

"Microsoft doesn't know how to..." is an unfounded disparagement. Microsoft definitely knows how to write software, okay? They're really good at it. They ship a lot of it. There are many people there who are brighter than you and I and they know their stuff cold. Microsoft is full of - legacy stuff that is really hard to change (many, many reasons for this, few of them pleasant but all of them real) - conflicting priorities (which bugs do we fix? will we destabilize the product if we fix them? are there more important things to do?) - political bullshit, in the atmosphere of which it is hard to do the right thing I left Microsoft three years ago, having spent 11 years there. I saw some howlingly bad software written (little of which shipped), and there are definitely groups there that are stronger than others, but I would never apply the phrase "fundamentally they don't know how to write software".

hga 11y ago
I go so far as to say, starting a bit over two decades ago, that one of the "secrets" of Microsoft's success is their long term ability to write software that basically works. As I mention in another part of this subthread (https://news.ycombinator.com/item?id=10352022 https://news.ycombinator.com/item?id=10352022), they beat their "Office" competitors in part by not losing that ability when all else but Borland did. (Borland didn't, but lost at higher levels of management, including buying one of those failed competitors.) As far as I can tell, general management incompetence, including of course "political bullshit", is most responsible for their post-XP problems (along with becoming too toxic for healthy peer companies to want work with them, but I'm not sure that matters when enough of the people at the top are so bad). Although ... what would you say was responsible for the failure of Longhorn? Wasn't that in part technical? Or did that derive from higher up?
- pmelendez 11y ago
  > what would you say was responsible for the failure of Longhorn? Wasn't that in part technical? Or did that derive from higher up? Bill Gates actually touched that topic in is Reddit AMA. If I remember correctly, the bar was set up too high (i.e relational file system) and within the constrains it was a big challenge and at some point they had to deliver.
  - hga 11y ago
    I also remember that a lot of it was going to based on .NET, and it wasn't mature enough/they weren't able to get it mature enough. The whole process was also impacted by security issues reaching a crisis level. But #1 would seem to be more ambition than Microsoft could deliver at the time.

by kabdib 11y ago

hga 11y ago

I go so far as to say, starting a bit over two decades ago, that one of the "secrets" of Microsoft's success is their long term ability to write software that basically works. As I mention in another part of this subthread (https://news.ycombinator.com/item?id=10352022 https://news.ycombinator.com/item?id=10352022), they beat their "Office" competitors in part by not losing that ability when all else but Borland did. (Borland didn't, but lost at higher levels of management, including buying one of those failed competitors.) As far as I can tell, general management incompetence, including of course "political bullshit", is most responsible for their post-XP problems (along with becoming too toxic for healthy peer companies to want work with them, but I'm not sure that matters when enough of the people at the top are so bad). Although ... what would you say was responsible for the failure of Longhorn? Wasn't that in part technical? Or did that derive from higher up?

pmelendez 11y ago
> what would you say was responsible for the failure of Longhorn? Wasn't that in part technical? Or did that derive from higher up? Bill Gates actually touched that topic in is Reddit AMA. If I remember correctly, the bar was set up too high (i.e relational file system) and within the constrains it was a big challenge and at some point they had to deliver.
- hga 11y ago
  I also remember that a lot of it was going to based on .NET, and it wasn't mature enough/they weren't able to get it mature enough. The whole process was also impacted by security issues reaching a crisis level. But #1 would seem to be more ambition than Microsoft could deliver at the time.