3 ms·

One thing to keep in mind is that there's a security angle to this as well. It is beneficial for a company to centralize all of its communication through one se

One thing to keep in mind is that there's a security angle to this as well. It is beneficial for a company to centralize all of its communication through one service which can be audited for security and also support all the features required to meet the internal Requirements. Having multiple tools multiplies the work needed to maintain security standards. Of course, I'm not saying that teams is more secure than competing products or that this will automatically improve security. The point is that it's a single option that's easier to manage. Outside of security, this also applies to cooperation between MS and Github teams. Teams helps with keeping common calendars, meeting invites, recordings and transcripts. Having more tools means that an adapter needs to exist between them and might be disincentivising communication, since engineers would prefer to work on their tasks rather than work around fixing soft problems.

danudey 4y ago
Teams is great for functionality, and also the worst, most unperformant application I've ever had to use for work. Somehow even Word/Excel on the web are more performant than Teams itself has ever been. It's slow to switch from "chats" to "chat rooms", and then to switch from whichever chat/room you're on to the one you want to be on. Allegedly they're working on this, but there's no way they're going to make it usable any time soon. I felt constant frustration using Teams and have it miss keypresses, fail to focus the text input in chats (I had to manually do so every time I changed chats), and remove all formatting and trim whitespace from code or text that I pasted, even if I pasted it into a code block (though for code blocks it only removed it when I send, so it looked fine until I hit enter). Trying to view or add integrations would often take several minutes for the modal dialog to finish loading (during which I couldn't use Teams). I also found frustrating sending files to people who then couldn't actually see them unless I manually granted them permissions. Why is this a thing? The QoL of developers at Github is going to drop significantly once they're forced onto Teams, because even after years and years it still feels like an early beta release where they haven't done a UX or optimization pass yet. My heart goes out to the Github team for this one.
bdlowery 4y ago
They aren’t centralizing their communication in teams. It’s being used for video conferencing. Everything else remains in slack. Read the image in the tweet, it’s only 100 words or so
- BazookaMusic 4y ago
  It's unlikely that they won't use it for more eventually if this works. They're probably playing it safe by mentioning only video conferencing. As an example, if meetings are made in teams and people comment during the meetings, their input will be in teams. Further communication around the meetings is likely to stay in teams. They're making it inconvenient to use slack or other means.

danudey 4y ago

Teams is great for functionality, and also the worst, most unperformant application I've ever had to use for work. Somehow even Word/Excel on the web are more performant than Teams itself has ever been. It's slow to switch from "chats" to "chat rooms", and then to switch from whichever chat/room you're on to the one you want to be on. Allegedly they're working on this, but there's no way they're going to make it usable any time soon. I felt constant frustration using Teams and have it miss keypresses, fail to focus the text input in chats (I had to manually do so every time I changed chats), and remove all formatting and trim whitespace from code or text that I pasted, even if I pasted it into a code block (though for code blocks it only removed it when I send, so it looked fine until I hit enter). Trying to view or add integrations would often take several minutes for the modal dialog to finish loading (during which I couldn't use Teams). I also found frustrating sending files to people who then couldn't actually see them unless I manually granted them permissions. Why is this a thing? The QoL of developers at Github is going to drop significantly once they're forced onto Teams, because even after years and years it still feels like an early beta release where they haven't done a UX or optimization pass yet. My heart goes out to the Github team for this one.

bdlowery 4y ago

They aren’t centralizing their communication in teams. It’s being used for video conferencing. Everything else remains in slack. Read the image in the tweet, it’s only 100 words or so

BazookaMusic 4y ago
It's unlikely that they won't use it for more eventually if this works. They're probably playing it safe by mentioning only video conferencing. As an example, if meetings are made in teams and people comment during the meetings, their input will be in teams. Further communication around the meetings is likely to stay in teams. They're making it inconvenient to use slack or other means.