3 ms·

> It's being forced onto billions of users, without the slightest bit of quality assurance or adherence to the basic practices of the art. whoa there, you don’

> It's being forced onto billions of users, without the slightest bit of quality assurance or adherence to the basic practices of the art. whoa there, you don’t know that. you think you do because you’re getting a ton of upvotes and you’re leaning into the feeling you had when you wrote that comment — the anti-Microsoft comment on a site known for its anti-microsoft comments. if you don’t work at Microsoft, you have very little hope of understanding the motivations of a team, a product manager, or even a single developer within Microsoft. there’s a lot more there than meets the eye, just like there is at any huge company.

jiggawatts 4y ago
Famously, Microsoft fired their entire QA team and now relies only on telemetry. They similarly fired their technical writing team, and now beg the public to write their documentation through pull-requests. I do know what Microsoft is or isn't doing. The evidence is in the pudding: opening a large text file in the new Notepad is orders of magnitude slower than any other editor on my system. This is a common failure mode that is trivially caught by testing. It's a well understood problem space, much like how databases "get slower" as the data volume increases, but the well understood solution is to use indexing to make this not occur. The fact that the Notepad team spent months (years?) working on a trivial text editor and never tested it with text files speaks volumes. If they had ever opened a large text file, they would have immediately noticed that a mistake had been made. Much like how if a database developer runs a query over large amounts of data, the missing indexes are immediately obvious. It takes a minute for Notepad to open a file that isn't even "huge". A minute isn't slow. It's broken. They shipped broken software to the public, at the scale of hundreds of millions or even billions of users. > understanding the motivations of a team, a product manager, or even a single developer within Microsoft. Clearly, performance and quality are never motivations at Microsoft.
- naikrovek 4y ago
forgotpwd16 4y ago
>if you don’t work at Microsoft, you have very little hope of understanding the motivations of a team, a product manager, or even a single developer within Microsoft Their motivations are irrelevant for an end-user. Their results are.
- naikrovek 4y ago
  It's important to understand that Microsoft are staffed by people just like us, trying to make things better. Except Microsoft get shit on daily simply because they are Microsoft. That stuff adds up and gets to people who work on things. If you don't think it should, I remind you that you can't take the humanity out of a human.
  - temphypercube 4y ago
    That doesn't justify horrifically slow applications. It just seems like Microsoft isn't fit for purpose. God, I'm glad I use linux.

jiggawatts 4y ago

Famously, Microsoft fired their entire QA team and now relies only on telemetry. They similarly fired their technical writing team, and now beg the public to write their documentation through pull-requests. I do know what Microsoft is or isn't doing. The evidence is in the pudding: opening a large text file in the new Notepad is orders of magnitude slower than any other editor on my system. This is a common failure mode that is trivially caught by testing. It's a well understood problem space, much like how databases "get slower" as the data volume increases, but the well understood solution is to use indexing to make this not occur. The fact that the Notepad team spent months (years?) working on a trivial text editor and never tested it with text files speaks volumes. If they had ever opened a large text file, they would have immediately noticed that a mistake had been made. Much like how if a database developer runs a query over large amounts of data, the missing indexes are immediately obvious. It takes a minute for Notepad to open a file that isn't even "huge". A minute isn't slow. It's broken. They shipped broken software to the public, at the scale of hundreds of millions or even billions of users. > understanding the motivations of a team, a product manager, or even a single developer within Microsoft. Clearly, performance and quality are never motivations at Microsoft.

naikrovek 4y ago

forgotpwd16 4y ago

>if you don’t work at Microsoft, you have very little hope of understanding the motivations of a team, a product manager, or even a single developer within Microsoft Their motivations are irrelevant for an end-user. Their results are.

naikrovek 4y ago
It's important to understand that Microsoft are staffed by people just like us, trying to make things better. Except Microsoft get shit on daily simply because they are Microsoft. That stuff adds up and gets to people who work on things. If you don't think it should, I remind you that you can't take the humanity out of a human.
- temphypercube 4y ago
  That doesn't justify horrifically slow applications. It just seems like Microsoft isn't fit for purpose. God, I'm glad I use linux.