Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm amazed by the extreme high quality of software that you've worked with. It doesn't come close to cracking any list for me. Tbh, I find it quite usable, with lots of useful features, and I can mostly count on it.

It really doesn't do anything especially bad IME. Teams on Mac just doesn't work at all. It's astonishing.



You’re on the “happy path”.

A lot of Microsoft software is like this, where they imagined one type of user and for them the product is great..

E.g.: Teams is okay for Project Managers permanently employed at some (single) mega corp.

For consultant developers switching between many clients, it’s a trash fire.

Both scenarios should work well, but Microsoft simply ignored the second case.

Why? Because it was designed by… PMs working at a single mega corp: Microsoft.


> Why? Because it was designed by… PMs working at a single mega corp: Microsoft.

Wow. When you put it that way...yeah, this explains absolutely everything about teams.

It bakes in so many assumptions about meeting flow as well. It's fine for ppt presentations but absolutely garbage for standups.


In the Windows desktop world, you can understand a lot by realising that Microsoft developers almost never install and configure Windows "from scratch".

They're given a preconfigured machine with a standard operating environment (SOE) image that has many small tweaks preconfigured. This is then connected to Active Directory and managed through Group Policy, which sets a bunch of configuration settings to sane values.

In other words, the people developing Windows are using it like 10% of their customers do (large enterprise), not like 90% of the customers (random individuals for home PCs or small business).

When I first realised this, a lot of little things suddenly "clicked" and made sense...

Some random examples of this:

Practically nobody at Microsoft gets given a PC or laptop with a HDR screen... so Windows does't do HDR properly.

Practically nobody at Microsoft has to worry about backups (it's centrally managed), so the backup capability built-in to Windows is trash and constantly broken and/or left to rot.

Everybody at Microsoft is "well connected" to the Azure cloud, so they assume every else is. Why not backup to One Drive? Uh.. because I'm satellite internet in the middle of nowhere!

Microsoft developers don't have to manage the SOE and its deployment process, so the tooling around this is... "not great".

Regional options, location, time zones, etc.. are all preconfigured and valid, so nobody at Microsoft thinks about what happens in "complex" cases... Like non-English-speakers using their products. Or being anywhere outside of the United States.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: