4 ms·

lots of hn readers use slack lots of hn slack users disliked the feature lots of hn slack users who disliked the feature went straight to hn to vote up any po

lots of hn readers use slack lots of hn slack users disliked the feature lots of hn slack users who disliked the feature went straight to hn to vote up any post complaining about it that's how communities around tech broadly tend to work

o-__-o 7y ago
a few people figured out how to change their workflow to deal with the change. turns out the same problem that exists between non-technical users and technical users exist between power-elite users and the non-PE users. when you try to show a non-technical user a different way to do things, they get really frustrated and give up easily because their entire mental model needs to change (they were used to clicking on an icon in a certain spot, goto a menu, select an option, get a dialog etc.). To them this represents a massive unknown if they do even one step wrong and so instead of accepting and using the new feature, regardless of the perceived benefit their anxiety takeover. The correlations here is astounding. I'm the kind of person who will vocally speak out about emacs vs vi or the pronunciation of "c-out" vs "sow-t", but the WYSIWYG editor didn't fundamentally break my mental model of Slack. I just learned to adapt, but seeing the blowback.. holy cow.
- Izkata 7y ago
  > or the pronunciation of "c-out" vs "sow-t" Wait, "cout" from C++? "Clout" is a real English word, I always figured it was pronounced the same minus the "l", which is neither of the versions you have there.
  - uryga 7y ago
    i always pronounced it as "see-out", since i figured the "c" refers to, well, C. seems in line with cout's docs which mention "the standard C output stream `stdout`"
  - o-__-o 7y ago
    I didn't do a good job, "see-out" vs "sowt" (the t is not hard)
    - Izkata 7y ago
      Still, I'm thinking of "kowt"
- swader999 7y ago
  I bow to your eliteness.
HeWhoLurksLate 7y ago
Cough, cough https://devrant.io https://devrant.io They closed the loop, folks!

o-__-o 7y ago

a few people figured out how to change their workflow to deal with the change. turns out the same problem that exists between non-technical users and technical users exist between power-elite users and the non-PE users. when you try to show a non-technical user a different way to do things, they get really frustrated and give up easily because their entire mental model needs to change (they were used to clicking on an icon in a certain spot, goto a menu, select an option, get a dialog etc.). To them this represents a massive unknown if they do even one step wrong and so instead of accepting and using the new feature, regardless of the perceived benefit their anxiety takeover. The correlations here is astounding. I'm the kind of person who will vocally speak out about emacs vs vi or the pronunciation of "c-out" vs "sow-t", but the WYSIWYG editor didn't fundamentally break my mental model of Slack. I just learned to adapt, but seeing the blowback.. holy cow.

Izkata 7y ago
> or the pronunciation of "c-out" vs "sow-t" Wait, "cout" from C++? "Clout" is a real English word, I always figured it was pronounced the same minus the "l", which is neither of the versions you have there.
- uryga 7y ago
  i always pronounced it as "see-out", since i figured the "c" refers to, well, C. seems in line with cout's docs which mention "the standard C output stream `stdout`"
- o-__-o 7y ago
  I didn't do a good job, "see-out" vs "sowt" (the t is not hard)
  - Izkata 7y ago
    Still, I'm thinking of "kowt"
swader999 7y ago
I bow to your eliteness.

HeWhoLurksLate 7y ago

Cough, cough https://devrant.io https://devrant.io They closed the loop, folks!