3 ms·

Why is this downvoted? (serious question) Where can I find the "code of conduct" for HN?

by tapan_k 10y ago

dahart 10y ago
One can only speculate on why either downvotes or upvotes occur, but it's fairly safe to assume someone disagreed with something said in the comment. The comment complains that the article provides nothing new and is feeding the rebase-vs-merge holy war. I would disagree with that, and it suggests to me the commenter didn't read the article. It's usually considered bad form to make comments on the headline without reading the article. This article in particular steers clear of all the holy war aspects of the rebase-vs-merge debate. I didn't downvote, but I speculate that's why it got downvoted. In the HN FAQ is a link to guidelines: https://news.ycombinator.com/newsfaq.html https://news.ycombinator.com/newsfaq.html https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html One of which is "Please resist commenting about being downvoted. It never does any good, and it makes boring reading." which is why you'll rarely see discussions about downvotes, and why usually speculation is all you get. ;)
- tapan_k 10y ago
  Thank you for the links to guidelines. This helps.
- hashkb 10y ago
  I read it. I thought it was a blog post and not part of their guide; so I can take back the timeliness/repetitive part of my complaint. I'm not complaining that it's feeding the holy war, just pointing out that it is one. My complaint is that we try to solve these issues with dogma, rather than expecting everyone to have a strong understanding of git, at which point all of the problems just sort of stop happening.
  - dahart 10y ago
    Then I'm another example in a long line of examples that demonstrate that speculation doesn't always produce high quality results. I've seen the holy war too, and I was impressed that this article took special care to stay completely out of it. I didn't see any dogma at all in this case, I saw helpful suggestions educating people about git and about when to make the call.
    - hashkb 10y ago
      Whatever, speculation is WAY more fun than empathy. (-:
CJefferson 10y ago
I downvoted it because of the suggestion that the only reason anyone would be a "merge person" is because they are afraid or stupid. It isn't helpful in any discussion to just say "side X are afraid and stupid.", and especially not without a good justification. No-one has (I believe) ever thought "Oh wow, I didn't realise I was being afraid and/or stupid, thanks for telling me. Now I'll change sides".
- hashkb 10y ago
  You're right. I'm frustrated from years of arguing against FUD; I didn't mean to say that 100% of merge-folk are ignorant or afraid, or that none of them have well reasoned points. I should have written "I'm saddened by how often I run into staunch defenders of the merge flow who, when put to the test, can't execute the equivalent rebase" because it happens all the time.

Why is this downvoted? (serious question) Where can I find the "code of conduct" for HN?

by tapan_k 10y ago

Why is this downvoted? (serious question) Where can I find the "code of conduct" for HN?

One can only speculate on why either downvotes or upvotes occur, but it's fairly safe to assume someone disagreed with something said in the comment. The comment complains that the article provides nothing new and is feeding the rebase-vs-merge holy war. I would disagree with that, and it suggests to me the commenter didn't read the article. It's usually considered bad form to make comments on the headline without reading the article. This article in particular steers clear of all the holy war aspects of the rebase-vs-merge debate. I didn't downvote, but I speculate that's why it got downvoted. In the HN FAQ is a link to guidelines: https://news.ycombinator.com/newsfaq.html https://news.ycombinator.com/newsfaq.html https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html One of which is "Please resist commenting about being downvoted. It never does any good, and it makes boring reading." which is why you'll rarely see discussions about downvotes, and why usually speculation is all you get. ;)

tapan_k 10y ago
Thank you for the links to guidelines. This helps.
hashkb 10y ago
I read it. I thought it was a blog post and not part of their guide; so I can take back the timeliness/repetitive part of my complaint. I'm not complaining that it's feeding the holy war, just pointing out that it is one. My complaint is that we try to solve these issues with dogma, rather than expecting everyone to have a strong understanding of git, at which point all of the problems just sort of stop happening.
- dahart 10y ago
  Then I'm another example in a long line of examples that demonstrate that speculation doesn't always produce high quality results. I've seen the holy war too, and I was impressed that this article took special care to stay completely out of it. I didn't see any dogma at all in this case, I saw helpful suggestions educating people about git and about when to make the call.
  - hashkb 10y ago
    Whatever, speculation is WAY more fun than empathy. (-:

CJefferson 10y ago

I downvoted it because of the suggestion that the only reason anyone would be a "merge person" is because they are afraid or stupid. It isn't helpful in any discussion to just say "side X are afraid and stupid.", and especially not without a good justification. No-one has (I believe) ever thought "Oh wow, I didn't realise I was being afraid and/or stupid, thanks for telling me. Now I'll change sides".

hashkb 10y ago
You're right. I'm frustrated from years of arguing against FUD; I didn't mean to say that 100% of merge-folk are ignorant or afraid, or that none of them have well reasoned points. I should have written "I'm saddened by how often I run into staunch defenders of the merge flow who, when put to the test, can't execute the equivalent rebase" because it happens all the time.