|
|
|
|
|
by dxdm
14 days ago
|
|
I don't think that the rule should regularly be broken. That's not what they say, and it's not what they mean. The strongest interpretation is: err on the side of not acting surprised at people's questions, because it tends to put people off asking them. I do think you're simply reading their rule in a way that's not intended by them. Could the rule be written to convey the intent more clearly? Yes, I think so. Is it only their own responsibility how the rule is interpreted? No, I don't think so. The hacker news guidelines ask us to: > respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith. This is good advice in general. It is your choice to pick an the interpretation that you disagree with the strongest, and subsequently use it to condemn them: "puts me off entirely", "no room for nuance", and (paraphrasing:) it's on them to prevent me from interpreting the rule in the most severe way. No. The spirit of the rule is clear. The nuance is there. What you do with it, that is all you. |
|
I share a similar apprehension, although it's hard to put into words exactly. Across the entire document, really. Like, it's clearly well intended, and not too bad of a match for things I would advocate myself. But at the same time it's suggestive of an impossibly high standard, and I have trauma from seeing "standards that can be interpreted as impossibly high" being applied inconsistently.
Especially the concept of "no subtle -isms": too often have I seen one side of a discussion accused of "-isms" they couldn't understand, while "-isms" they found more sympathetic/obvious went unnoticed. (That's, er, tangentially related to how I ended up making an account here in the first place.)