Live data from Hacker News

Very Short Reply Expected

blog.vrypan.net

111–120 of 232 posts

Re: Very Short Reply Expected

#111
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.

Re: Very Short Reply Expected

#112

Earlier quoted context omitted.

This is not social awkwardness. This is social efficiency.

No, you've got it all wrong! Geeks aren't socially awkward, they're socially "efficient" Social conventions aren't established by protocol drafts, they're organic. Also, people write long replies for a reason. Wording indicates emotional state. If you have trouble reading emotional state, you don't care. If, like most people, you do care, then this proposal is ridiculous. An example: "How about we schedule lunch next…

Personally, I find the latter response just disrespectful of my time. If all you want/need to say is you can't make it, don't write a bloody novel! All I need is an answer.

There's a time and place for long communication and it's in person. Not in an email.

Re: Very Short Reply Expected

#113

Annnnnnd this is why geeks have a reputation for social awkwardness.

I'm glad I'm not the only person who had this reaction.

Sheesh, how hard is it to type out "A one word response would be fine." It takes me less than 10 seconds to type that. C'mon.

Re: Very Short Reply Expected

#116
post #74

If it means "very short reply OK" why isn't it VSRO? "Expected" almost sounds too demanding to me...like you'll actually be disappointed if I write a little more.

"Very short reply Welcome" VSRW was discussed elsewhere to make clear that it is an invitation but not an expectation.

Re: Very Short Reply Expected

#117

Earlier quoted context omitted.

BTW. Since we're talking about efficiency down this thread, here's a very nice example of optimizing communication: http://wiki.lesswrong.com/wiki/Crocker%27s_rules I wish this concept was more widely known though. EDIT: original description ( http://www.sl4.org/crocker.html ) is dead but I found it's contents in cache, so I'm quoting it below: http://webcache.googleusercontent.com/search?q=cache:http://... Declaring…

Link should be: http://wiki.lesswrong.com/wiki/Crocker%27s_rules

Edited, thanks!

Re: Very Short Reply Expected

#119
post #65

Earlier quoted context omitted.

How is communication about consensus? You can put others off and still communicate "correctly".

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…

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 brusqueness, your point comes across, then it's effective communication.

Re: Very Short Reply Expected

#120
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.

I see you enjoy neardoc/heredoc
Post reply on HN