Hacker News new | past | comments | ask | show | jobs | submit
There's no rule against being surprised, and especially not against _ever_ being surprised. They are asking people not to express surprise, real or not, when responding to a question, as a courtesy to the person asking. Like: Keep your surprise in check in situations when it's not helping.

I don't think that's too much to ask, just like it's generally considered preferable to not chew with your mouth open when in company, or talk to people with food in your mouth.

They even acknowledge that they expect these rules to not be followed all the time.

I'm surprised that you read it as a general prohibition of being surprised. ;)

Edit: Sorry, wrote my reply before I saw your substantial edits where you clarify your position and distinguish between "positive" and "negative" surprise. I agree there's a better way express surprise. The rule clearly wants people to avoid putting other people down by creating a feeling of "wow, how can you not know this". That's the spirit of the rule, and I guess it could be expressed better. I don't think they'd have a problem if someone managed to turn the surprise into a positive, but to do that, it's good to be mindful that it's often perceived negatively.

Sorry for the ninja edits. Writing from phone and didn't think there'd be people replying right away.

Seems like we're in agreement. But I reiterate that it's not a good rule if it should be regularly broken, for the good.

Thus, for a project that's been around for seemingly a very long time, it's hard to imagine that they haven't had ample time and feedback to vastly improve the wording of it all. Thus, they seem to be content that it expresses exactly what they want it to.

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.

loading story #48957032
loading story #48957694