Skip to main content
Commonmark migration
Source Link

##What tone should I strike in comments?

What tone should I strike in comments?

Comments should always be civil and informative. Take the time and effort to make them so, or refrain from commenting and let the closing system and the FAQ do the work for you.

When writing a comment, be sure to explain why a user should do something. Saying "make your question more specific", for example, does not explain why someone should do that. If a quick explanation was added to that comment, people would understand why you said what you said, and they will understand more about stack exchange and be less likely to do that again.

Remember that everyone who reaches the page can read your comment, not just the person you are addressing. The only thing more discouraging than reaching the site via Google and not finding an answer to your question is seeing curt, brusque, or uncivil chatter in the comments.

###Examples of good and bad comments

Examples of good and bad comments

Bad

  • Stack Overflow is not your personal research assistant. <-- because it is snarky.

    Stack Overflow is not your personal research assistant. <-- because it is snarky.

     
  • Improve your accept rate. <-- Because it doesn't explain anything.

    Improve your accept rate. <-- Because it doesn't explain anything.

Good

  • What output did you expect to see, and what did you see instead?

  • Could you add more details about X?

  • Do you have a link, citation, or reference for the claim you are making in this post?

  • Sharing your research helps everyone. Tell us what you found and why it didn’t meet your needs.

##What tone should I strike in comments?

Comments should always be civil and informative. Take the time and effort to make them so, or refrain from commenting and let the closing system and the FAQ do the work for you.

When writing a comment, be sure to explain why a user should do something. Saying "make your question more specific", for example, does not explain why someone should do that. If a quick explanation was added to that comment, people would understand why you said what you said, and they will understand more about stack exchange and be less likely to do that again.

Remember that everyone who reaches the page can read your comment, not just the person you are addressing. The only thing more discouraging than reaching the site via Google and not finding an answer to your question is seeing curt, brusque, or uncivil chatter in the comments.

###Examples of good and bad comments

Bad

  • Stack Overflow is not your personal research assistant. <-- because it is snarky.
     
  • Improve your accept rate. <-- Because it doesn't explain anything.

Good

  • What output did you expect to see, and what did you see instead?

  • Could you add more details about X?

  • Do you have a link, citation, or reference for the claim you are making in this post?

  • Sharing your research helps everyone. Tell us what you found and why it didn’t meet your needs.

What tone should I strike in comments?

Comments should always be civil and informative. Take the time and effort to make them so, or refrain from commenting and let the closing system and the FAQ do the work for you.

When writing a comment, be sure to explain why a user should do something. Saying "make your question more specific", for example, does not explain why someone should do that. If a quick explanation was added to that comment, people would understand why you said what you said, and they will understand more about stack exchange and be less likely to do that again.

Remember that everyone who reaches the page can read your comment, not just the person you are addressing. The only thing more discouraging than reaching the site via Google and not finding an answer to your question is seeing curt, brusque, or uncivil chatter in the comments.

Examples of good and bad comments

Bad

  • Stack Overflow is not your personal research assistant. <-- because it is snarky.

  • Improve your accept rate. <-- Because it doesn't explain anything.

Good

  • What output did you expect to see, and what did you see instead?

  • Could you add more details about X?

  • Do you have a link, citation, or reference for the claim you are making in this post?

  • Sharing your research helps everyone. Tell us what you found and why it didn’t meet your needs.

added 70 characters in body
Source Link
user102937
user102937

##What tone should I strike in comments?

Comments should always be civil and informative. Take the time and effort to make them so, or refrain from commenting and let the closing system and the FAQ do the work for you.

When writing a comment, be sure to explain why a user should do something. Saying "make your question more specific", for example, does not explain why someone should do that. If a quick explanation was added to that comment, people would understand why you said what you said, and they will understand more about stack exchange and be less likely to do that again.

Remember that everyone who reaches the page can read your comment, not just the person you are addressing. The only thing more discouraging than reaching the site via Google and not finding an answer to your question is seeing curt, brusque, or uncivil chatter in the comments.

###Examples of good and bad comments

Bad

  • Stack Overflow is not your personal research assistant. <-- because it is snarky.
  • Improve your accept rate. <-- Because it doesn't explain anything.

Good

  • What output did you expect to see, and what did you see instead?

  • Could you add more details about X?

  • Do you have a link, citation, or reference for the claim you are making in this post?

  • Sharing your research helps everyone. Tell us what you found and why it didn’t meet your needs.

##What tone should I strike in comments?

Comments should always be civil and informative. Take the time and effort to make them so, or refrain from commenting and let the closing system and the FAQ do the work for you.

When writing a comment, be sure to explain why a user should do something. Saying "make your question more specific", for example, does not explain why someone should do that. If a quick explanation was added to that comment, people would understand why you said what you said, and they will understand more about stack exchange and be less likely to do that again.

Remember that everyone who reaches the page can read your comment, not just the person you are addressing. The only thing more discouraging than reaching the site via Google and not finding an answer to your question is seeing curt, brusque, or uncivil chatter in the comments.

###Examples of good and bad comments

Bad

  • Stack Overflow is not your personal research assistant.
  • Improve your accept rate.

Good

  • What output did you expect to see, and what did you see instead?

  • Could you add more details about X?

  • Do you have a link, citation, or reference for the claim you are making in this post?

  • Sharing your research helps everyone. Tell us what you found and why it didn’t meet your needs.

##What tone should I strike in comments?

Comments should always be civil and informative. Take the time and effort to make them so, or refrain from commenting and let the closing system and the FAQ do the work for you.

When writing a comment, be sure to explain why a user should do something. Saying "make your question more specific", for example, does not explain why someone should do that. If a quick explanation was added to that comment, people would understand why you said what you said, and they will understand more about stack exchange and be less likely to do that again.

Remember that everyone who reaches the page can read your comment, not just the person you are addressing. The only thing more discouraging than reaching the site via Google and not finding an answer to your question is seeing curt, brusque, or uncivil chatter in the comments.

###Examples of good and bad comments

Bad

  • Stack Overflow is not your personal research assistant. <-- because it is snarky.
  • Improve your accept rate. <-- Because it doesn't explain anything.

Good

  • What output did you expect to see, and what did you see instead?

  • Could you add more details about X?

  • Do you have a link, citation, or reference for the claim you are making in this post?

  • Sharing your research helps everyone. Tell us what you found and why it didn’t meet your needs.

added 64 characters in body
Source Link
user102937
user102937

##What tone should I strike in comments?

Comments should always be civil and informative. Take the time and effort to make them so, or refrain from commenting and let the closing system and the FAQ do the work for you.

When writing a comment, be sure to explain why a user should do something. Saying "make your question more specific", for example, does not explain why someone should do that. If a quick explanation was added to that comment, people would understand why you said what you said, and they will understand more about stack exchange and be less likely to do that again.

Remember that everyone who reaches the page can read your comment, not just the person you are addressing. The only thing more discouraging than reaching the site via Google and not finding an answer to your question is seeing curt, brusque, or uncivil chatter in the comments.

###Examples of good and bad comments

Bad

  • Stack Overflow is not your personal research assistant.
  • Improve your accept rate.

Good

  • What output did you expect to see, and what did you see instead?

  • Could you add more details about X?

  • Do you have a sourcelink, citation, or reference for the claim you are making in this post?

  • Sharing your research helps everyone. Tell us what you found and why it didn’t meet your needs.

##What tone should I strike in comments?

Comments should always be civil and informative. Take the time and effort to make them so, or refrain from commenting and let the closing system and the FAQ do the work for you.

When writing a comment, be sure to explain why a user should do something. Saying "make your question more specific", for example, does not explain why someone should do that. If a quick explanation was added to that comment, people would understand why you said what you said, and they will understand more about stack exchange and be less likely to do that again.

Remember that everyone who reaches the page can read your comment, not just the person you are addressing. The only thing more discouraging than reaching the site via Google and not finding an answer to your question is seeing curt, brusque, or uncivil chatter in the comments.

###Examples of good and bad comments

Bad

  • Stack Overflow is not your personal research assistant.
  • Improve your accept rate.

Good

  • What output did you expect to see, and what did you see instead?

  • Could you add more details about X?

  • Do you have a source?

  • Sharing your research helps everyone. Tell us what you found and why it didn’t meet your needs.

##What tone should I strike in comments?

Comments should always be civil and informative. Take the time and effort to make them so, or refrain from commenting and let the closing system and the FAQ do the work for you.

When writing a comment, be sure to explain why a user should do something. Saying "make your question more specific", for example, does not explain why someone should do that. If a quick explanation was added to that comment, people would understand why you said what you said, and they will understand more about stack exchange and be less likely to do that again.

Remember that everyone who reaches the page can read your comment, not just the person you are addressing. The only thing more discouraging than reaching the site via Google and not finding an answer to your question is seeing curt, brusque, or uncivil chatter in the comments.

###Examples of good and bad comments

Bad

  • Stack Overflow is not your personal research assistant.
  • Improve your accept rate.

Good

  • What output did you expect to see, and what did you see instead?

  • Could you add more details about X?

  • Do you have a link, citation, or reference for the claim you are making in this post?

  • Sharing your research helps everyone. Tell us what you found and why it didn’t meet your needs.

deleted 479 characters in body; deleted 12 characters in body
Source Link
user102937
user102937
Loading
added 79 characters in body; added 5 characters in body; added 76 characters in body
Source Link
Jeff Atwood
  • 311.4k
  • 107
  • 889
  • 1.3k
Loading
added info explaining why comments should be more informative
Source Link
user160606
user160606
Loading
added 16 characters in body
Source Link
user102937
user102937
Loading
deleted 1634 characters in body
Source Link
user102937
user102937
Loading
deleted 226 characters in body
Source Link
user102937
user102937
Loading
There's actually already a FAQ for the first three sections... Added constructive advice for accept rate (needs to be shorter though)
Source Link
Shog9
  • 454.3k
  • 203
  • 1.3k
  • 1.9k
Loading
Post Made Community Wiki by user102937
deleted 1 characters in body; deleted 14 characters in body
Source Link
user102937
user102937
Loading
added 69 characters in body; deleted 4 characters in body; added 3 characters in body; added 3 characters in body; added 4 characters in body
Source Link
user102937
user102937
Loading
Source Link
user102937
user102937
Loading