|
|
|
|
|
|
by garren
2563 days ago
|
|
|
Is that a law? I feel like that should be a law: If you think you don't like X, just wait until your company forces you to use Microsoft Y. - _emacsomancer_'s law I've used slack for school, and it was pretty useful. I'm using Teams at work, and it seems remarkably less so. I'm not sure if it's because nobody's comfortable using it for anything other than skype meetings, or because it somehow seems less intuitive or well thought out as slack. Probably a bit of both. One thing that kind of kills me - we use visualstudio.com too for git (incidentally, it's interesting to see a strong tfs team struggling with git - vs/git integration is useful only if you're relative comfortable with git in the first place), and there doesn't seem to be any kind of strong integration between vs.com and ms teams. That's weird. I see my team on teams, I converse with them on teams, I have access to my backlog items on teams (with an azure plugin), but why can't I see my team's board? vs.com's UI takes some getting used to, but at the very least it seems like it should be accessible, with very little additional work, within teams. Teams feels a lot like a half-baked (maybe 3/4 baked) response to Slack that could really be so much more. |
|
|
Is Teams the bastard stepchild of Microsoft? I haven't used Teams, but I recall reading a personal account probably 6 years ago about what working on Google+ was like. Every time something integrated to it, it was a mess and dragged the other products down. Word got around and groups actively avoided the Google+ team and were scrambling for justification as to why they shouldn't get integrated.
0 chance I could find the comment now, but it stuck with me all these years.