891–900 of 1001 posts
For what it’s worth, Mattermost is an open source alternative built for engineers by engineers. The interface is markdown.
In their defence (not the defence of the WYSIWYG box itself) - they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability, etc etc. You have to remember Slack's target persona is probably no longer the Engineer (If it ever was) - it's more likely a much less tech-savvy employee who finds WYSIWYG editors very handy to create rich text inputs. I guess…
> they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability I have never worked at a company that did user testing or if they did it was always done in a way or interpreted in a way to back up the designer's opinion. I don't think I've once in my entire 40 yr career seen a designer test with users, find out something was bad, and change their design…
Earlier quoted context omitted.
Huh? Why not? It seems completely relevant.
It's also relevant to those who would take it away. Widespread adoption will compel them to break it.
Earlier quoted context omitted.
Please ask them what they think of the ‘drafts’ section. I’m so fed up of losing chats to that section.
Join the hundreds of people complaining in this twitter thread, I put my beef with it in there too. https://twitter.com/SlackHQ/status/1135955676545585164
This reminds me of Atlassian's god-awful WYSIWYG editor. In both cases, I get that some users can't or don't like to use a machine grammar/markup, however simple. For some people markup is bad UX. Give them a WYSIWYG; that's fine. But don't remove the markup editor if your WYSIWYG editor is anything but a perfect one-two-one replacement for markup (and I have never seen one that satisfies that). IIRC there was a time…
> This reminds me of Atlassian's god-awful WYSIWYG editor. Oh my goodness: triggered. I've barred the use of Confluence at our company specifically because of this. "But, but, we used it at blah company." "Yes, so did I at blahblah company, and it was unbelievably crappy and made me angry every time I had to edit a document: we're not using it." I DO NOT want to have to use what amounts to an extremely buggy, caprici…
I have contacted them, and they replied me with this Lucas (Slack) Nov 20, 9:15 PM PST Hi there, Thank you for taking the time to write in and provide this feedback. I apologize for the disruption to your existing workflows. Our aim is to build an editor that works for all Slack users to better format their messages and clearly communicate in channels, regardless of their technical expertise. While we are taking all…
I have contacted them, and they replied me with this Lucas (Slack) Nov 20, 9:15 PM PST Hi there, Thank you for taking the time to write in and provide this feedback. I apologize for the disruption to your existing workflows. Our aim is to build an editor that works for all Slack users to better format their messages and clearly communicate in channels, regardless of their technical expertise. While we are taking all…
Boy they can fuck right off with that corporate doublespeak bullshit. Commitment to users means respecting that people have different preferences, and options let you respect that.
Specific bug gripes aside: I see this editor as emblematic of Slack's broader shift away from what I think it should be (primarily synchronous chat; irc with a friendlier ui and integrated bouncer features) towards what many people seem to want to use it as (async-heavy pseudo-replacement for email where I get to sit and watch the "...is typing" indicator flicker while somebody writes an essay at me). My rule of thum…
I personally have no problem with the hybridization of sync/async communication. That's where everything is headed. People send emails and sometimes expect them to be delivered and/or read immediately. OTOH, people send messages over these "chat" services that aren't time sensitive, simply because it's easy and available. My problem is that all these networks are proprietary and isolated. When someone comes up with a…
Tons of people said this early on, but the people who make decisions for team tooling/workflows apparently didn't think that was as important. Symptomatic of the disconnect between what most engineers think of as "quality" versus others.