The main reasons are: 1) Because it isn't always worth the cost 2) Because we don't always fully understand the systems we are modifying Which hearkens back to, "Don't fix it if it ain't broke". Inefficient is not automatically broke.
In this case I don't think that these reasons apply. Introducing a VSRE on the initiator side, or a Short Response, Not An Asshole on the responding side would be a worthwhile change with a manageable side effect. Don't fix it if it ain't broke seems to run counter to innovation. I'd try for improvement on a functional system if there's a positive expected outcome.
Because if you take the trouble to write that out, there will still be slightly more pressure on the receiver to reciprocate by giving a more formal reply, despite the surface content. I think "how hard is it?" is the wrong question. We should be asking "how can this be better?". It doesn't take very long to type something like "as far as I know", but we still routinely use acronyms like AFAIK, because as long as eve…
AFAIK, IMHO, INAL, etc. work because they are acronyms for very common phrases. Intelligent people can reason out their meaning based on context without you having to spell them out. That's why they are popular and why they work. There was never a global memo "Hey everybody we're going to start using AFAIK now." VSRE doesn't work. It's better to just type out what you want to say in this case.
You just say "VSRE doesn't work" without mentioning that the only reason is that people don't already say it. That's my point. Maybe we can agree that we shouldn't jump straight to the acronym. But if we want this kind of custom, and I do, it has to start somewhere, not with a global memo but with people just doing it. I'm just going to start saying "short reply ok". With any luck that will catch on, and then we can abbreviate to "SRO" or whatever people wind up using, and the world will be an ever so slightly more efficient place.
Protocols are about consensus, almost by definition. In computer protocols, we get the consensus before we start using the protocol. In social interactions, we're molding the protocol as we use it. As for communicating "correctly", it's a matter of (mostly) definitions and circumstances whether putting people off and "correct" communication are consistent. You may have transmitted the correct information to someone's…
In computer protocols, we get the consensus before we start using the protocol. VSRP analogue in computing: Unannounced, start omitting headers in response to HTTP requests. They are unnecessary baggage that gets in the way of the actual content of the message.
Better analog, start sending
X-ACCEPT-NO-HEADERS: true
or something in your request, which allows the responding party to omit headers in the reply (or not).
I can't speak for the author, but sometimes the emails contain messages like "Major emergency - stop what you're doing right now" where, if I didn't get the email until 30 minutes later, could be problematic.
I have a filter, which pops up a notification only for certain emails. Those from my boss.
so all of your emergencies must come through your boss... that would not work for me
> Are you really that damn busy that you can't spend a minute or less writing a more natural and conversational reply It's not that simple. If I'm in the middle of a coding binge I can switch over and fire off a 'VSRE' without losing place. Converting that into a 'sociable' reply requires a mental context switch out of coding land and into human land. That doesn't cost me 2 minutes, It costs me half an hour [0]. So e…
When I'm programming, I close all email and instant messaging applications, as well as put my phone on Airplane mode. I find limiting interruptions in this way to be incredible for mental focus. I highly recommend it, if you don't already do this (?). I also use the following website to set a timer for however long I have to program (whether it be a 15 minute sprint or a luxurious 90 minute block): http://www.online-…
>When I'm programming, I close all email and instant messaging applications
You can't do that when you code and also run a business. I'd love for this to catch on, I'm going to discuss it with my team at least for IM.
In the early days of the telephone, there was some debate about the proper way to start and terminate a discussion. Many were fond of starting a discussion with 'ahoy', ending with 'that is all'. Alas, 'hello' and 'goodbye' won the competition. That is all.
Now that I know this I am _very_ angry that 'ahoy' and 'that is all' didn't carry the day.
Never mind what carried the day -- I'm adopting this protocol starting now, convention be damned!