3 ms·

(And no one noticed for the first few hours)

• paleotrope 3y ago
  It wasn't completely out. We were using it all day yesterday for video and.phone conferences without issue. Chats were slow and image loading was hit or miss.
• analog31 3y ago
  It's funny you say that, because it's true. I didn't notice. A contractor called and we tried setting up a Teams meeting so he could show me some stuff, and it just didn't work. So we quickly switched over to another tool that he uses for showing his screen, and I put my phone in "speaker" mode. It never occurred to either of us that Teams had actually gone down. Each of us assumed it was our IT.
  • lostlogin 3y ago
    > Each of us assumed it was our IT It sort of was, they chose Teams. I say this as someone who uses Teams and could probably get us moving away from it but the inertia is real.
• silisili 3y ago
  We were among the companies that switched from Slack to Teams. Slack was absolutely overflowing with work activity, side chats, a few random channels. Hundreds if not thousands a day. Everyone hates Teams so much they only seem to use it as absolute last resort. I see about 10 total messages a day, if that. So yeah, it took us a long time to realize it was even down.
  • lostlogin 3y ago
    Has the reduced chatter helped, or hindered work?
    • silisili 3y ago
      For me, hindered. We're a remote company, and rather silod at that, so watching chats helped me see who does what, things going on, even help where I could. With Teams it just feels cold and lonely, to be honest. I'd say if everyone knew everything, and just wanted to code all day, it probably would have helped work as there is less random chatter too. But I'm not sure that's ever realistic for a company.
• belter 3y ago
  That is a joke normally used for Azure...