8 ms·

I never truly understand issues people have with these things. I tune my notifications as to avoid true interruptions and filter most false positives by quick l

I never truly understand issues people have with these things. I tune my notifications as to avoid true interruptions and filter most false positives by quick looking. I see people at my office (and different companies!) saying they quit Slack/Whatever because they were getting bombarded by notifications... They had the option to notify on all messages. ¬¬ Even then, come on, I cannot believe experience hasn’t taught most of you how to handle quick interruptions. I usually just quick look at the notification to see if it’s really urgent. Otherwise it may be 7-10 minutes until I actually check the application, in case I’m doing some heavy thinking/coding session. There are true interruptions like constant notifications, people physically talking to you about other things, and stuff, that while you cannot really tune them all out, you should be able to handle better with 2-3 years of experience. I read a lot of people on these forums with many more years not being able to cope with that. I will die still unable to believe it was the norm, and not the exception :(

freddie_mercury 7y ago
I think they are best understood as the modern equivalent of circa 2000 era virtue signalling "I don't watch TV, we don't even have one in our house". Except now people do it online on HN because their IRL friends are sick of hearing them talk about it.
protonimitate 7y ago
Yeah I'm not sure why the slack good / slack bad discussion warrants as much discussion as it does. It's just a communication tool. Either it works for you personally, or it does not. I don't think it deserves a weekly HN first page discussion though.
- themoat 7y ago
  I didn't read this as a slack good / slack bad article at all. At my current job I was asked to join a client's slack group (added without my consent) and it was a nightmare. The problems have nothing to do with notifications or interruptions, but it gives them the implicit understanding that I am a custom developer for their needs. Since they can reach me at any time, they assume that I am going to fix their bugs, add their features, etc. It circumvents what I think is the proper procedure for work. I suspect that's more the heart of why the author is saying they aren't going to join their client's slack group.
  - RHSeeger 7y ago
    This seems a lot like you making assumptions about their expectations and/or acting on their expectations/your assumptions; rather than acting the way you think is correct. If you aren't their personal dev, then don't be one. The only thing my presence in a client's slack means is that I (and/or the other people from my company in their slack) am reasonable first point of contact. I'm perfectly happy telling them that their problem is not one I can solve (or choose to prioritize), and that they should touch base with <appropriate person>.
    - themoat 7y ago
      I guess my story was unnecessary, but I commented that I didn't read the article the way the person I responded to (and the person above him as well). I don't understand why the top rated comment is worded in a way that sounds like the article was bashing slack because the Author of the article doesn't understand how to focus...when I read the article and saw nothing that led me to believe the top level comment was on topic. So I commented. If I am ok to carry on this tangent we are already on, I cannot wrap my head around a scenario where it would be appropriate for a member of a SaaS company, dev/PM/CTO/QA or what have you to be in a slack channel for one of their clients. It's completely unprofessional and should be avoided.
iamnotacrook 7y ago
My problem (with Skype, so ok that's two problems) is people just put "hi" or "hello" and then the choice is to either ignore them and hope they'll get around to actually asking the question, or give in and say "hi" (passive aggressive or "hi, what's up" (I don't care what's up - you started it). I can't think of a polite way to say "please don't just type "hi"" without making it sound like I think I'm special, but at the same time ignoring them outright seems rude. They know I'm here because of the presence indicator.
- jedberg 7y ago
  Just ignore when they say hi. They'll eventually learn that they don't get a response. If they actually talk to you about your "rudeness" explain that you only respond if it seems urgent, and "hi" isn't urgent.
- choward 7y ago
  This drives me crazy too. Would you send an email that just said "hi"? Didn't think so. Is it that hard to just say "hi, [question]"? Instead I have to reply and then wait for them to type their question since I've already been interrupted.
- ummonk 7y ago
  Ironically, I once got feedback from my team lead that when I would start with my question without first pinging with a generic "hello", it seemed demanding.
  - lliamander 7y ago
    Would you say "<Question>" or "Hi! <Question>"? The former could seem demanding, but if they're offended by latter then the situation is hopeless.
    - ummonk 7y ago
      I would usually say “Question: <question>”. The latter might have been okay; after the feedback I just switched to “hey I’m stuck” or “Hey I’ve got a question” and asked the question after he replied, which he was happy with.
aloknnikhil 7y ago
People are lazy. They can't get themselves to change the defaults. It's a barrier they see too high. Pretty much why iOS is great because it "just works". Designing an HCI (Human-Computer Interaction) system is really hard.
dumbfounder 7y ago
This is mostly about setting expectations with the client. If they slack you most of the time they expect to hear back soon, or else they probably would have used email. So they opted to make it clear and just not use slack. Makes sense to me.
smacktoward 7y ago
> I never truly understand issues people have with these things. I tune my notifications as to avoid true interruptions and filter most false positives by quick looking. You've answered your own question. The product is distracting by default. The savvy user can cut down on the distractions by configuring notifications, teaching themselves how to scan messages, etc., but if there's one thing we know from 70 years of writing software it's that most users accept whatever defaults you give them. Sometimes that's because they don't know they can reconfigure the software; sometimes it's because they do know they can reconfigure it, but can't figure out how; sometimes it's because they know how to reconfigure it, but are too busy with other things to do so. But the underlying reason doesn't really matter, what matters is the general effect: the default experience the software provides is the experience that most users are going to have with it. And with Slack, the default experience is distracting. > Even then, come on, I cannot believe experience hasn’t taught most of you how to handle quick interruptions. How many threads have been posted on HN complaining about things that take programmers out of their state of "flow"? How many programmers have you met who are happy to hear their phone ring when they're working? > There are true interruptions like constant notifications, people physically talking to you about other things, and stuff, that while you cannot really tune them all out, you should be able to handle better with 2-3 years of experience. 2-3 years studded with bouts of lost productivity is a lot of lost productivity. A product that tells me my life is "only" going to suck for 2-3 years while I learn how to use it is not a product I am going to be thrilled to use.
- anbotero 7y ago
  > How many threads have been posted on HN complaining about things that take programmers out of their state of "flow"? How many programmers have you met who are happy to hear their phone ring when they're working? Those are what the true interruptions are about. A notification? I'm sorry, but after less than a month one learns how not to let a simple sound or notification distract you. Constant phone ringing is a true interruption; one ringing loop? Not so much. > 2-3 years studded with bouts of lost productivity is a lot of lost productivity. A product that tells me my life is "only" going to suck for 2-3 years while I learn how to use it is not a product I am going to be thrilled to use. Handling interruptions is about not letting them make you lose much productivity, but after all, this is for true interruptions. They will affect you, but there are ways to lessen the effect. If people allow other people to constantly interrupt them without setting clear boundaries/priorities, it's your (or your Manager) problem. I usually set things in the clear from the beginning, and after two or three times, it'll never happen again. But again, these are true interruptions: Some are necessary, and those which are not can be handled better.
hbosch 7y ago
> I never truly understand issues people have with these things. I tune my notifications as to avoid true interruptions and filter most false positives by quick looking. The problem isn't the notifications here. Sure, I can tune my notifications to my preference, but when you're a resident in a client's Slack the expectation is that they can directly message you, anytime, for any reason, and for any size request. Like the article says, Slack does not encourage deep and meaningful messaging – it's more like a text. I have found that opening a channel like this almost always brings with it a firehouse of small changes requested in bursts, whereas a single e-mail encourages bundling of issues and requests into minimal amounts of messages. The worst thing about Slack is the constant "10:00am: hey HBOSCH, can you do X?", "10:15am: oh, and can you also do Y?", "10:47am: and while you're at it, maybe you could handle Z? haha sorry for being crazy!", "10:49am: <silly gif>". It's so annoying. I also tune my notifications effectively by using Do Not Disturb mode on my iPhone from 12:00AM to 11:59PM, along with the "Bedtime" feature in my alarms. This keeps my phone quiet all day, only allowing phone calls from people on my Favorites list to come through, and the Bedtime function in Alarms keeps my whole device totally silent from 10pm to 6am. But that's not helpful if a client is trying to reach me at 8am EST when they need an emergency update before a morning meeting.
- davedx 7y ago
  > The problem isn't the notifications here. Sure, I can tune my notifications to my preference, but when you're a resident in a client's Slack the expectation is that they can directly message you, anytime, for any reason, and for any size request. This is kind of true. I work with several partners of our ecom platform using Slack. Most of them are not that responsive, and that's fine - Slack is a chat app but it's still asynchronous! As long as people answer reasonable queries in a reasonable time (so e.g. within the working day) then it's fine. I never expect instant answers. Manage expectations I guess?
- RHSeeger 7y ago
  > when you're a resident in a client's Slack the expectation is that they can directly message you, anytime, for any reason, and for any size request Why do you think that? The client's I'm in slack with certainly don't expect that.
joemi 7y ago
A distraction is still a distraction. Why not get rid of one if it's not needed?

freddie_mercury 7y ago

I think they are best understood as the modern equivalent of circa 2000 era virtue signalling "I don't watch TV, we don't even have one in our house". Except now people do it online on HN because their IRL friends are sick of hearing them talk about it.

protonimitate 7y ago

Yeah I'm not sure why the slack good / slack bad discussion warrants as much discussion as it does. It's just a communication tool. Either it works for you personally, or it does not. I don't think it deserves a weekly HN first page discussion though.

themoat 7y ago
I didn't read this as a slack good / slack bad article at all. At my current job I was asked to join a client's slack group (added without my consent) and it was a nightmare. The problems have nothing to do with notifications or interruptions, but it gives them the implicit understanding that I am a custom developer for their needs. Since they can reach me at any time, they assume that I am going to fix their bugs, add their features, etc. It circumvents what I think is the proper procedure for work. I suspect that's more the heart of why the author is saying they aren't going to join their client's slack group.
- RHSeeger 7y ago
  This seems a lot like you making assumptions about their expectations and/or acting on their expectations/your assumptions; rather than acting the way you think is correct. If you aren't their personal dev, then don't be one. The only thing my presence in a client's slack means is that I (and/or the other people from my company in their slack) am reasonable first point of contact. I'm perfectly happy telling them that their problem is not one I can solve (or choose to prioritize), and that they should touch base with <appropriate person>.
  - themoat 7y ago
    I guess my story was unnecessary, but I commented that I didn't read the article the way the person I responded to (and the person above him as well). I don't understand why the top rated comment is worded in a way that sounds like the article was bashing slack because the Author of the article doesn't understand how to focus...when I read the article and saw nothing that led me to believe the top level comment was on topic. So I commented. If I am ok to carry on this tangent we are already on, I cannot wrap my head around a scenario where it would be appropriate for a member of a SaaS company, dev/PM/CTO/QA or what have you to be in a slack channel for one of their clients. It's completely unprofessional and should be avoided.

iamnotacrook 7y ago

My problem (with Skype, so ok that's two problems) is people just put "hi" or "hello" and then the choice is to either ignore them and hope they'll get around to actually asking the question, or give in and say "hi" (passive aggressive or "hi, what's up" (I don't care what's up - you started it). I can't think of a polite way to say "please don't just type "hi"" without making it sound like I think I'm special, but at the same time ignoring them outright seems rude. They know I'm here because of the presence indicator.

jedberg 7y ago
Just ignore when they say hi. They'll eventually learn that they don't get a response. If they actually talk to you about your "rudeness" explain that you only respond if it seems urgent, and "hi" isn't urgent.
choward 7y ago
This drives me crazy too. Would you send an email that just said "hi"? Didn't think so. Is it that hard to just say "hi, [question]"? Instead I have to reply and then wait for them to type their question since I've already been interrupted.
ummonk 7y ago
Ironically, I once got feedback from my team lead that when I would start with my question without first pinging with a generic "hello", it seemed demanding.
- lliamander 7y ago
  Would you say "<Question>" or "Hi! <Question>"? The former could seem demanding, but if they're offended by latter then the situation is hopeless.
  - ummonk 7y ago
    I would usually say “Question: <question>”. The latter might have been okay; after the feedback I just switched to “hey I’m stuck” or “Hey I’ve got a question” and asked the question after he replied, which he was happy with.

aloknnikhil 7y ago

People are lazy. They can't get themselves to change the defaults. It's a barrier they see too high. Pretty much why iOS is great because it "just works". Designing an HCI (Human-Computer Interaction) system is really hard.

dumbfounder 7y ago

This is mostly about setting expectations with the client. If they slack you most of the time they expect to hear back soon, or else they probably would have used email. So they opted to make it clear and just not use slack. Makes sense to me.

smacktoward 7y ago

> I never truly understand issues people have with these things. I tune my notifications as to avoid true interruptions and filter most false positives by quick looking. You've answered your own question. The product is distracting by default. The savvy user can cut down on the distractions by configuring notifications, teaching themselves how to scan messages, etc., but if there's one thing we know from 70 years of writing software it's that most users accept whatever defaults you give them. Sometimes that's because they don't know they can reconfigure the software; sometimes it's because they do know they can reconfigure it, but can't figure out how; sometimes it's because they know how to reconfigure it, but are too busy with other things to do so. But the underlying reason doesn't really matter, what matters is the general effect: the default experience the software provides is the experience that most users are going to have with it. And with Slack, the default experience is distracting. > Even then, come on, I cannot believe experience hasn’t taught most of you how to handle quick interruptions. How many threads have been posted on HN complaining about things that take programmers out of their state of "flow"? How many programmers have you met who are happy to hear their phone ring when they're working? > There are true interruptions like constant notifications, people physically talking to you about other things, and stuff, that while you cannot really tune them all out, you should be able to handle better with 2-3 years of experience. 2-3 years studded with bouts of lost productivity is a lot of lost productivity. A product that tells me my life is "only" going to suck for 2-3 years while I learn how to use it is not a product I am going to be thrilled to use.

anbotero 7y ago
> How many threads have been posted on HN complaining about things that take programmers out of their state of "flow"? How many programmers have you met who are happy to hear their phone ring when they're working? Those are what the true interruptions are about. A notification? I'm sorry, but after less than a month one learns how not to let a simple sound or notification distract you. Constant phone ringing is a true interruption; one ringing loop? Not so much. > 2-3 years studded with bouts of lost productivity is a lot of lost productivity. A product that tells me my life is "only" going to suck for 2-3 years while I learn how to use it is not a product I am going to be thrilled to use. Handling interruptions is about not letting them make you lose much productivity, but after all, this is for true interruptions. They will affect you, but there are ways to lessen the effect. If people allow other people to constantly interrupt them without setting clear boundaries/priorities, it's your (or your Manager) problem. I usually set things in the clear from the beginning, and after two or three times, it'll never happen again. But again, these are true interruptions: Some are necessary, and those which are not can be handled better.

hbosch 7y ago

> I never truly understand issues people have with these things. I tune my notifications as to avoid true interruptions and filter most false positives by quick looking. The problem isn't the notifications here. Sure, I can tune my notifications to my preference, but when you're a resident in a client's Slack the expectation is that they can directly message you, anytime, for any reason, and for any size request. Like the article says, Slack does not encourage deep and meaningful messaging – it's more like a text. I have found that opening a channel like this almost always brings with it a firehouse of small changes requested in bursts, whereas a single e-mail encourages bundling of issues and requests into minimal amounts of messages. The worst thing about Slack is the constant "10:00am: hey HBOSCH, can you do X?", "10:15am: oh, and can you also do Y?", "10:47am: and while you're at it, maybe you could handle Z? haha sorry for being crazy!", "10:49am: <silly gif>". It's so annoying. I also tune my notifications effectively by using Do Not Disturb mode on my iPhone from 12:00AM to 11:59PM, along with the "Bedtime" feature in my alarms. This keeps my phone quiet all day, only allowing phone calls from people on my Favorites list to come through, and the Bedtime function in Alarms keeps my whole device totally silent from 10pm to 6am. But that's not helpful if a client is trying to reach me at 8am EST when they need an emergency update before a morning meeting.

davedx 7y ago
> The problem isn't the notifications here. Sure, I can tune my notifications to my preference, but when you're a resident in a client's Slack the expectation is that they can directly message you, anytime, for any reason, and for any size request. This is kind of true. I work with several partners of our ecom platform using Slack. Most of them are not that responsive, and that's fine - Slack is a chat app but it's still asynchronous! As long as people answer reasonable queries in a reasonable time (so e.g. within the working day) then it's fine. I never expect instant answers. Manage expectations I guess?
RHSeeger 7y ago
> when you're a resident in a client's Slack the expectation is that they can directly message you, anytime, for any reason, and for any size request Why do you think that? The client's I'm in slack with certainly don't expect that.

joemi 7y ago

A distraction is still a distraction. Why not get rid of one if it's not needed?