3 ms·
I also work weird hours at times, but hold my messages. > Please don't take a message from me outside your normal hours to mean I want or need an immediate res
by georgyo 4y ago
I also work weird hours at times, but hold my messages.
> Please don't take a message from me outside your normal hours to mean I want or need an immediate response unless the message is directly talking about a production outage in which case i'll be explicit about that.
This still means they need to wake up everytime a message is received. There are likely other mechanisms for waking them during an outage, but the pressure it still there that it could be related to an outage that did not page them specially.
Similarly, getting a message while you are at a BBQ, family event, or bar will make you start thinking about the problem right away. Potentially removing their mind from the moment they are currently in.
> If you're around and you want to spend a few hours debating the merits of embedding a lua interpreter into a data processing pipeline vs trying to figure out how to droplessly reload golang code great, if not, we can pick it up the next time we're both around.
You may be saying this honestly, but many people, especially junior new hires will feel pressure none the less. They really to make good impressions and impress people.
- nicoburns 4y ago> This still means they need to wake up everytime a message is received. Agreed if urgent messages are going through the same channel as non-urgent. Otherwise, message sent doesn’t necessarily imply message received, and I reckon it makes more sense to encourage people to turn off work notifications out of hours.
- Handytinge 4y agoThis was pretty clearly (I thought) covered later in the same comment: > Setting the actual expectations works great. Some people respond simply by saying that they won't put slack on their phone, or will turn notifications for slack off and I'm fine with that (having their number to call for actual emergencies).