Live data from Hacker News

Very Short Reply Expected

blog.vrypan.net

181–190 of 232 posts

Re: Very Short Reply Expected

#181
post #177

Earlier quoted context omitted.

As we are not organic beings, clearly it would be foolish of us to accept such unnecessary inefficiencies.

I agree with the second part of your statement. Why not make things more efficient where we can?

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.

Re: Very Short Reply Expected

#182
post #173
post #171

Earlier quoted context omitted.

> 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…

Why wouldn't you wait until you take a break to reply to emails? You're choosing to switch over during a "coding binge" when you don't need to.

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.

Re: Very Short Reply Expected

#183
post #18

This is what I use Jabber for--Jabber messages have an implicit VSRE attached. In practice, it's just like email except that the replies are usually short. For me, Jabber messages get delivered to the same places on both my computer and phone, and take about the same amount of effort to respond to. It has the added benefit of potentially being a real-time conversation as well--this sometimes happens with a flurry of…

You could always use something like ShortMail. It's basically Twitter, but for email.

It's been around long enough now that you probably don't have to worry about it going away anytime soon, and its users really like it.

(I am not affiliated)

http://shortmail.com/

Re: Very Short Reply Expected

#184

Earlier quoted context omitted.

Many of my most truncated email responses have come from executives and other businesspeople. VSRE sounds great for anyone with limited time, and sufficient trust. I'd feel good using something like this with another person who I know well, or know to be businesslike. I wouldn't use this with someone I don't know well in a social context.

I think that for a lot of the execs truncation is a well established way to communicate self-importance.

It's more about effective communication than power games. Brevity is natural when you have to communicate with lots of people via email and your main priority is getting shit done. What's funny is that for random/cold emails, i'm far more likely to reply if I can respond in a line or two without being rude.

Re: Very Short Reply Expected

#185
post #126
post #101

I love this. I'm also extremely fond of EOM (short for End Of Message. An email with a short subject and no body). Often I send EOMs to imply a VSRE. For example, "Grill tonight? Have burgers. Off work @ 6. EOM" Very interested in learning others.

NT: No text This one is shorter than the rest, and easy to grok. VSRE OR EOM? I'd have to look those up.

Between NT and EOM why does being shorter make it more obvious, you'd need to look after whichever one you hadn't heard before. If anything I'd say EOM is easier to guess, due to its similarity with other acronyms: EOL (coding) EOP (business) where EO always stands for End Of.

Re: Very Short Reply Expected

#186
post #144

I think people tend to grossly exaggerate how many emails they really do get. Are you really that damn busy that you can't spend a minute or less writing a more natural and conversational reply that indicates to the other person that you're reciprocating the amount of thought and effort they invested in their message? I agree with some others here in saying that this is awkward. You don't strive for efficiency in soc…

> natural and conversational reply that indicates to the other person that you're reciprocating the amount of thought and effort they invested in their message?

"If it was hard to write, it should be hard to read."

"If it took long to write, it should take long to reply to."

Re: Very Short Reply Expected

#188
I guess VSRE is a very appropriate method to skip the social formalities and discomforting feeling it brings along with it. Some people (like me) like to keep it brief and to the point, rather than pulling strings of over-politeness. It doesn't mean we are rude or something, its just that we are comfortable with this way of interaction at work place.

Re: Very Short Reply Expected

#189
post #177

Earlier quoted context omitted.

I agree with the second part of your statement. Why not make things more efficient where we can?

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.

Re: Very Short Reply Expected

#190
post #136
post #119

Earlier quoted context omitted.

You can't communicate effectively without a protocol/language/etc, but communicating is not about consensus; it's about communicating ideas/thoughts/etc. Consensus is a part of communication, not its aim. I agree that not offending/annoying someone is beneficial and might outweigh the message you have to communicate, but that isn't relevant to discussion about the efficiency of the protocol. If in spite of brusquenes…

Think of the "consensus" as the embedded state within a communication. In a feudal society a lord might send a written missive to the King or Queen, and if they did it would contain a ton of horribly polite boilerplate, because the consensus of the time on both sides was that anything less was disrespectful. It is very possible that your lack of words in a given communication sends a point across that you never inten…

Sure, but that doesn't speak to my point that consensus is a component of communication, not its primary aim.
Post reply on HN