Not the point of the article, but this is a personal bugbear of mine - no it wasn't. Text-based communication is asynchronous. It's rude to _expect_ that someone is present and available if you message them out of the blue (or, rather - rude to get upset if they don't immediately reply), but it's not rude to send the message in the first place. Particularly - it is never correct to send a Delayed Message on Slack "because it's the evening/weekend and I don't want to bother them". The four possible outcomes are:
* You send delayed; they could have benefitted from the information earlier (e.g. there's an outage overnight and your delayed message contained helpful information) -> your delay had a negative effect
* You send delayed; they read the message when they come online again during business hours -> your delayed message had no impact (assuming you correctly guessed their business hours)
The only situation where "sending delayed" has a positive impact is where there is a culture whereby a message _must_ be replied to at the time it's sent. In such a situation, you need to fix that broken culture rather than working around it with delay-hacks.