zlacker

[parent] [thread] 6 comments
1. jrockw+(OP)[view] [source] 2023-11-18 05:34:28
I don't think it's a joke. I would find it patronizing unless I'm already on a first name basis with the commenter through some prior relationship.
replies(3): >>EFreet+N >>Fillig+nc >>lijok+bJ
2. EFreet+N[view] [source] 2023-11-18 05:40:35
>>jrockw+(OP)
It happened to me recently on a list where I post under my real name, and yes, it's irritating, especially if it is someone you never met, and they are disagreeing with you.
3. Fillig+nc[view] [source] 2023-11-18 07:25:37
>>jrockw+(OP)
Really? Referring to someone by first name is perfectly ordinary where I’m from, regardless of relationship. If someone doesn’t want me to do that, I’d expect them to introduce themselves as “Mr. so-and-so”, instead.
replies(2): >>TeMPOr+Nd >>jrockw+Ue
◧◩
4. TeMPOr+Nd[view] [source] [discussion] 2023-11-18 07:41:05
>>Fillig+nc
It's not the first name alone, it's also the sentence structure. "Hey John, did you hear about..." sounds perfectly normal even when talking on-line to strangers. "John, you misunderstand..." is appropriate if you're their parent or spouse or otherwise in some kind of close relationship.
replies(1): >>jrockw+Ye
◧◩
5. jrockw+Ue[view] [source] [discussion] 2023-11-18 07:50:33
>>Fillig+nc
In person, sure, that's totally normal. It's unusual on a forum for a few reasons:

1) The comments are meant to be read by all, not just the author. If you want to email the author directly and start the message with a greeting containing their name ("hi jrockway!"), or even just their name, that's pretty normal.

2) You don't actually know the person's first name. In this case, it's pretty obvious, since the user in question goes by what looks like <firstname><lastname>. But who knows if that's actually their name. Plenty of people name their accounts after fictional people. It would be weird to everyone if your HN comment to darthvader was "Darth, I don't think you understand how corporate law departments work." Darth is not reading the comment. (OK, actually I would find that hilarious to read.)

3) Starting a sentence with someone's name and a long pause (which the written comma heavily implies) sounds like a parent scolding a child. You rarely see this form outside of a lecture, and the original comment in question is a lecture. You add the person's name to the beginning of the comment to be extra patronizing. I know that's what was going on and the person who was being replied to knows that's what was going on. The person who used that language denies that they were trying to be patronizing, but frankly, I don't believe it. Maybe they didn't mean to consciously do it, but they typed the extra word at the beginning of the sentence for some reason. What was that reason? If to soften the lecture, why not soften it even more by simply not clicking reply? It just doesn't add up.

4) It's Simply Not Done. Open any random HN discussion, and 99.99% of the time, nobody is starting replies with someone's name and a comma. It's not just HN; the same convention applies on Reddit. When you use style that deviates from the norm, you're sending a message, and it's going to have a jarring effect on the reader. Doubly jarring if you're the person they're naming.

TL;DR: Don't start your replies with the name of the person you're replying to. If you're talking with someone in person, sure, throw their name in there. That's totally normal. In writing? Less normal.

◧◩◪
6. jrockw+Ye[view] [source] [discussion] 2023-11-18 07:51:38
>>TeMPOr+Nd
You have explained this much more concisely than me.
7. lijok+bJ[view] [source] 2023-11-18 12:03:51
>>jrockw+(OP)
Is it the first name or the personal touch that would make you feel patronized? What if you read a reply “… a 24 year old, such as yourself, will know …”.
[go to top]