At least for me, that's a time-to-leave signal.
Teams biggest "Feature" is that is part of the Office 364 Suite, a lot of the layout and other issues are simply forgiven since there are no additional licensing or costs to use it over Slack if you are already on Office 364 Enterprise
Teams is "good enough" for most organizations and is improving,
That is microsoft current plan, be "good enough"
Out of curiosity, what do you think of the Stylish userscript that enables a compact mode in Teams and offers dark and light themes?
I still prefer an App instead of the browser, but that's just personal preference.
Teams is free as part of an Office 365 subscription (just like Sharepoint and all the other crap they bundle with it), which is what definitely makes it an existential threat to Slack, because now Slack is competing with Microsoft's very strong Office monopoly.
The fact that you can create a group with some channels, add your files there and edit them together, have a wiki, have a (not very good) kanban board etc. makes it a pretty complete experience. Some of the tools they release needs more polish and some tools are by themselves much worse than stand alone competitors but having everything in one is pretty nice.
Then there is sharepoint, oh, and onedrive, and they all come in the same package so everyone uses something else.
At a previous company, we had slack and MS Teams side by side, to trial out MS Teams. Everyone preferred Slack by a huge margin. We were told to get use to Teams, because Teams is free.
Guess what, it was fine.. no notable productivity lose going from slack to teams. If anything, team's sharepoint file integration is much better than slack, for keeping a single source of truth.
The Android app in particular has trouble. And muting is all-or-nothing.
I've also had corrupted channels, I even escalated to Microsoft once.
Doesn't matter, since it comes with Office so it basically costs $0.
It's crap, but that's not stopping my employer from replacing literally everything they can with it. Even our desk phones, purportedly.
So if that is indeed the case here, then it does indicate some problems.
I’m amazed that I’m still talking about this :)
Not only is that a miserable experience, but I think it's also a recipe for a product that only gets worse.
That's the over reaction part. The fact that two engineers feels uncomfortable expressing their feelings, says very little about the culture or values in their company.
It could be that they are just too introverted or insecure to speak up about most things, or that they have a good relationship with the fellow engineers in that other team, and don't feel like ruining it by telling them, that their contributions to the product sucks.
But that's not what was said. It was correctly described as a possible management problem, a signal. If your notion is that one should leave at the first signal, that's something you bring to it.
Anyhow, we have evidence that the problem is more widespread. It's obvious from the HN reaction that quite a lot of people hate this feature, engineers especially. But still it was released. If you want to hypothesize a situation that makes that unimportant, you have to dream up a lot more than two extremely insecure engineers.
Terrible UI choice. It makes no sense.
Don't get me wrong, the "you'll get an answer" is almost always the same "thank you for your input" but at least it creates a Zendesk ticket from a paying customer, in contrast to whining on HN or Twitter, where I am about dead certain no corporate OKR is influenced
```
one
```
```
two
```
Now the behaviour is to ask you every time to apply formatting. There is an option for "don't ask again" which I tried assuming it would make autoformatting the default, but it turns off the behaviour completely with no way to get it back!
Unfortunately it must be done every time, no autoformatting by default it seems.
Still...I could have swore I had tried that anyway. Huh.
The trick seems to be to add a blank final line, otherwise, it will not include the last line you typed in a code block.
e.g.
> * My quoted bullet point
Glad my only use is a comms channel for my Ingress group.
The concept seems to originate from Netscape's CEO and the acronym exists since 2006, according HiPPO FAQ: http://bitly.com/HIPPOExplained
And where the link goes to, obviously. No idea if this counts toward the Bitly link open rate.
1) don’t need to be logged in for the + to work
2) I’ve not seen it increment the clicks by visiting the + stats page, but can’t speak authoritatively on that.
High Importance Person Pushing Own (desires??)?
It is usually used when a company has no actual data to work on and therefore goes with the "obvious" as defined by "the boss" (Hippo).
Not that it is necessarily true. There could be lots of data that some people are not aware of and that only senior people are privy to, but if that is not shared with the team developing the software then that is in itself not a great sign.
The only way I know how to make a good design, is to have a good Product Owner. Prototyping helps a little bit, User testing absolutely not. You can have five different PO working on the same epic and still get a bad design, but it only takes one to find the perfect solution.
That input box story is not different. They could have made the WYSIWYG feature compatible with the "old" input method by changing the visual without altering the character flow (eg: The <star>brown<star> fox). Apparently, no one thought of that...
If I'm imagining it correctly, it should work like this:
writing `help` will render it inline. A rendered `help`^H becomes an un-rendered `help
The rendering doesn't need to show the backticks, but it seems to me that it's perfectly reasonable to have it exist from the text-editing perspective.
The real problem might be that hitting <star><star>help<star><star><LEFT_KEY> can either move invisibly between one of the two stars (technically correct), or jump a star to place the cursor just after p (visually correct).
I would think the best solution is to have all editing keys (eg backspace, delete, insert-then-type) be technically correct, and all movement keys (eg arrow keys) be visually correct.
I think this is also how Typora does its markdown rendering, which was functionally intuitive in my experience (I stopped using it because it slowed down severely with any file larger than like 300 characters, so a worthless text editor, but UI-wise it worked well)
It really resonated with my thoughts, how I've viewed the tech world and my (tiny) part in it.