Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Horror of Microsoft Teams

medium.com

Post reply on HN
Print view View original

301–310 of 344 posts

Re: The Horror of Microsoft Teams

#301

Post by wink »

casparz wrote: post #263
broth wrote: post #195

Earlier quoted context omitted.

Back in my senior year of high school during Spanish class I naively used NET SEND to send a message to one of my classmates. The only problem was that I failed to specify the user in the command and instead used *. This ended up sending a message to all computers in the school district. I remember the computer administrator coming into the class saying “Are you aware one of your students is sending messages to the e…

A classmate did the same, although the outcome was far worse. We studied at university in the medical faculty, which happened to be housed in the academic hospital. We found out the hard way that the network was not segregated, his netsend command crashed all the ICU terminals...

Just that the guy isn't to blame. That's like saying "By switching off the lights in the break room I shutdown the power in all the operation rooms"

Re: The Horror of Microsoft Teams

#302

Post by tremon »

empath75 wrote: post #72

This thread should give some much needed perspective on all the people who assume MS is going to destroy slack. I bet slack destroys outlook before teams destroys slack.

Microsoft will destroy Slack the same way it destroyed Netscape: by pushing its own inferior product for free.

Re: The Horror of Microsoft Teams

#303

Post by laurentb »

lozenge wrote: post #230
moksly wrote: post #196

Earlier quoted context omitted.

I think Teams is exactly excellent because it allows you to secure your collaboration tool. Especially valuable post GDPR where you really don’t want your non-tech savy employers putting privacy data into some online Trello board, or slack/discord for that matter. The fact that teams is just part of your 365 platform is soooo awesome in non-tech enterprise that it’s hard to describe just how useful it is. But basical…

"I love how integrated it is but I had to write code to remove the integration that was counterproductive" I get it, but it seems contradictory, and your workaround is probably beyond reach for many smaller businesses.

a simpler version of that workaround can be built with a powershell script (and hell, with a little bit of fiddling around, you can even use PowerApps as a front UI) in less than 2 days if not one morning.

Re: The Horror of Microsoft Teams

#305

Post by hn_throwaway_99 »

zaphoyd wrote: post #284
acdha wrote: post #131

Earlier quoted context omitted.

I’m curious what was so great about it: when we did the comparison even the Atlassian maintainers picked Slack.

It was a focused product. Native apps, high performance, no funny business. Yes, it lacked some features that the newer stuff had, but it did the team chat part really well and got out of your way. Deploying web apps lets you iterate faster, stuff features in faster without ending up with different capabilities across the group of apps. Sometimes the ability to add features too easily is abused to add too many featur…

When it was up. The frequent outages on HipChat circa 2014 or so got to be unbearable, and we switched to Slack at that point, and were much happier.

Re: The Horror of Microsoft Teams

#306

Post by atoav »

nevir wrote: post #48
mullingitover wrote: post #7

> "This means that if someone does @${channel_name} you will get an alert. MS have not implemented muting as a feature. Secondly, for all those automatic/admin channels, you can’t unsubscribe yourself (or at least not with the default policies). Brilliant, isn’t it? Unavoidable alerts that any idiot on any channel can annoy people with." At my last job we figured out the fastest way to get your company off Teams: add…

Our CEO gave up on slack long ago. Email is the best way to get their attention.

And to be honest Email is ok. Email is like writing a letter and it should be.

You write it, think about it send it.

In a chat you just type and send as you think and decoding that stuff in hindsight is more work.

I’d rather get one focused and well thought out mail than 20.messages of which a quarter shouldn’t even bother me.

There is no real reason why you couldn’t write Slack messages as well composed as an email. But nearly nobody does.

Re: The Horror of Microsoft Teams

#307

Post by foxX »

addicted wrote: post #117
huffmsa wrote: post #82

Earlier quoted context omitted.

> That being said, the Teams UX will slowly and steadily improve You think that they people who brought us "The Word Ribbon" and Metro UI are going to make things better? That's not how M$FT rolls. Their customer base is deathly allergic to change. They lose their minds if things change perceptibly from what they looked like when they bought the system.

I don't know. The word ribbon was miserable to begin with but it has reached a point, thanks to a bunch of UI improvements, where it's far preferable to the classic menu for many people (at least the majority of people I've met). The word ribbon is definitely an example to follow. Metro isn't, because , wtf. They can't make up their mind.

The Office Ribbon is ESPECIALLY useful on OS X where there's a menu system as well with the builtin Help -> search in menus box. With that, one doesn't ever need to even look at that abomination of a ribbon.

Re: The Horror of Microsoft Teams

#308

Post by theboulevardier »

mysterydip wrote: post #120
mullingitover wrote: post #7

> "This means that if someone does @${channel_name} you will get an alert. MS have not implemented muting as a feature. Secondly, for all those automatic/admin channels, you can’t unsubscribe yourself (or at least not with the default policies). Brilliant, isn’t it? Unavoidable alerts that any idiot on any channel can annoy people with." At my last job we figured out the fastest way to get your company off Teams: add…

Reminds me of the NET SEND command in windows 2000-xp. Allowed sending a popup text message to specific (or all with a wildcard!) machines on a network. Sure there were times where such a feature would be convenient ("server going down for maintenance, please save your work", etc), but overall ripe for abuse. They disabled it in a service pack and took it out altogether in subsequent versions.

I had so much fun with that back in school. Our machines were running Win NT 4.0 and and the computers were labelled with a the network name. So I would check the names of the machines my friends were on, or the whole class if I was feeling bold and then create a batch file to send them hundreds of messages.

Re: The Horror of Microsoft Teams

#309

Post by brynjolf »

throwaway7000 wrote: post #96

Disclosure: Microsoft employee. Using a throwaway. Satya, please don't track me down and fire me. I've never agreed so heavily with a headline and disagreed so vehemently with the actual content. Some of this is right, but a big chunk is wrong and I think misses some of the most egregious horrors of Teams. I used Slack professionally before in a fairly large org (>200). Two things the author got wrong: First - things…

Reading this thread [0] on your Uservoice shows that no progress has been done since August 2018 on notifications management for the end user. I'm sure you allow control when you create a channel but convincing the teammanager who very day pings the entire channel to say their work hours that day is impossible so that feature is more or less useless. The fact that you can praise coworkers with unicorns is implemented before proper notifications has made me go from believing in the future of Teams to now praising Slack. It is maddening.

[0] https://microsoftteams.uservoice.com/forums/555103-public/su...

Re: The Horror of Microsoft Teams

#310

Post by brynjolf »

Reading this thread [0] on their Uservoice shows that no progress has been done since August 2018 on notifications management for the end user. I'm sure they allow control when you create a channel but convincing the teammanager who very day pings the entire channel to say their work hours that day is impossible so that feature is more or less useless. The fact that you can praise coworkers with unicorns, being implemented before proper notifications, has made me go from believing in the future of Teams to now praising Slack. It is maddening.

[0] https://microsoftteams.uservoice.com/forums/555103-public/su...

Post reply on HN