You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Asking any question should specify the information that the questioner is missing and expecting from the questionee. Simply typing "?" is disrespectful at the very least, but serves no communicational purpose, isn't even funny. It should be avoided just as saying "hello" in business communication.
I'd like whoever to expand this site with a section regarding "?" or create a sister site devoted to that issue. I am open to participate in server/domain costs etc.
The text was updated successfully, but these errors were encountered:
I completely agree with @paboum's viewpoint on the use of "?" in communication. It's frustrating when a message lacks context and simply consists of a question mark. Such messages can be quite unproductive and leave a lot of room for misunderstanding. I'm all for the idea of creating a sister site dedicated to addressing this issue.
If this initiative moves forward, I'd be more than willing to also contribute to server/domain costs and assist with development if necessary.
Well, underspecified questions are unproductive in many ways, however plain "?" is an extreme example, a marker of total disregard for question's function, asking it just for the sake of asking. Rectifying it will also have impact on all other cases, this is a "mother of all" underspecified questions. I wouldn't divide the efforts to any subclass at the moment.
Asking any question should specify the information that the questioner is missing and expecting from the questionee. Simply typing "?" is disrespectful at the very least, but serves no communicational purpose, isn't even funny. It should be avoided just as saying "hello" in business communication.
I'd like whoever to expand this site with a section regarding "?" or create a sister site devoted to that issue. I am open to participate in server/domain costs etc.
The text was updated successfully, but these errors were encountered: