3 ms·

I think you and I mostly agree but I will try to address the possible source of your disagreement with his phrasing. @jbk's original phrasing was: I'm waiting

by sah2ed 9y ago

I think you and I mostly agree but I will try to address the possible source of your disagreement with his phrasing. @jbk's original phrasing was: I'm waiting for your patch. I'm very happy for your volunteering. You probably think his first sentence is sarcasm but it is not for two reasons: 1. He followed it up with a gentler "I'm very happy for your volunteering." 2. I've been online long enough to know that his phrasing is a bit odd, a hint that the commenter is likely not a native speaker. For a bit more context regarding #2, my suspicion is not unfounded. I remember the @jbk nickname from this highly upvoted post [0] last year, where he did something in the interest of the VLC project that a lot of people would find incredibly difficult to do under similar circumstances. [0] https://news.ycombinator.com/item?id=15372048 https://news.ycombinator.com/item?id=15372048

jancsika 9y ago
> 1. He followed it up with a gentler "I'm very happy for your volunteering." "Gentler" seems like a euphemism to me. I read it instead as passive aggression which is generally considered rude and not a productive way of communicating with people. Normal communication: 1. X makes an unreasonable demand of developer Y. "Users expect Z, you devs should always do Z." 2. Developer Y counters X's unreasonable demand with simple-to-follow reasoning: "I understand where you are coming from, but there are important technical reasons why we cannot do Z. Unless you have the time to dive into the code to understand those technical details (and perhaps even become a developer yourself in the process), you're just going to have to trust us on this point." Benefits: clarity, positive example, trollproof. Costs: several sentences, restraint. Passive Aggressive Communication: 1. X makes an unreasonable demand of developer Y. "Users expect Z, you devs should always do Z." 2. Developer Y tries to "teach" X not to make unreasonable demands by making a similarly unreasonable demand. If devs should always do Z, and if current devs are too busy to do Z, then it should be so obvious that X must become a dev that Y will imply it in the response: "Thanks for volunteering!" Benefit: brevity Cost: confusion, consequent anger/humiliation in X that makes it harder for them to learn the ostensible lesson, troll food, negative example for future devs to follow, scary to potential devs, etc. Edit: typo

by sah2ed 9y ago

jancsika 9y ago

> 1. He followed it up with a gentler "I'm very happy for your volunteering." "Gentler" seems like a euphemism to me. I read it instead as passive aggression which is generally considered rude and not a productive way of communicating with people. Normal communication: 1. X makes an unreasonable demand of developer Y. "Users expect Z, you devs should always do Z." 2. Developer Y counters X's unreasonable demand with simple-to-follow reasoning: "I understand where you are coming from, but there are important technical reasons why we cannot do Z. Unless you have the time to dive into the code to understand those technical details (and perhaps even become a developer yourself in the process), you're just going to have to trust us on this point." Benefits: clarity, positive example, trollproof. Costs: several sentences, restraint. Passive Aggressive Communication: 1. X makes an unreasonable demand of developer Y. "Users expect Z, you devs should always do Z." 2. Developer Y tries to "teach" X not to make unreasonable demands by making a similarly unreasonable demand. If devs should always do Z, and if current devs are too busy to do Z, then it should be so obvious that X must become a dev that Y will imply it in the response: "Thanks for volunteering!" Benefit: brevity Cost: confusion, consequent anger/humiliation in X that makes it harder for them to learn the ostensible lesson, troll food, negative example for future devs to follow, scary to potential devs, etc. Edit: typo