Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

There is a certain amount of questions that are absolutely trivial in nature: How to format a date, how to concatenate a string, et cetera. Questions that could be solved by taking a look into the manual.

Random examples from the tags I frequent:

What those OPs need is a link to the right manual, which we should give them. But the question serves no purpose. They don't even have a use by being searchable, because any sane search query would lead to the actual manual as the first hit.

Jeff discusses the possibility of introducing a new close reason for this over at Scifi.stackexchange.com. According to Robert's suggestion there, it could go like this:

general reference: this question is too basic; the answer is indexed in any number of general internet reference sources designed specifically to find that type of information.

Please please implement this.

Add a field (like the "enter duplicate ID here" popup) for users to suggest the correct manual link:

The suggested links would then be shown in a block in the top section of the question, like duplicate links.

Also, the amount of reputation earnable from these trivial questions is appalling. I'm sure a great portion of most high-rep users' points (including mine) is from answering "what was that function for replacing a string again?" type questions. This dilutes the value of reputation as a measure of true expertise a great deal.

I would suggest that answers to questions that get closed as "general reference" are made community wiki retroactively, taking away any reputation earned.

There is a certain amount of questions that are absolutely trivial in nature: How to format a date, how to concatenate a string, et cetera. Questions that could be solved by taking a look into the manual.

Random examples from the tags I frequent:

What those OPs need is a link to the right manual, which we should give them. But the question serves no purpose. They don't even have a use by being searchable, because any sane search query would lead to the actual manual as the first hit.

Jeff discusses the possibility of introducing a new close reason for this over at Scifi.stackexchange.com. According to Robert's suggestion there, it could go like this:

general reference: this question is too basic; the answer is indexed in any number of general internet reference sources designed specifically to find that type of information.

Please please implement this.

Add a field (like the "enter duplicate ID here" popup) for users to suggest the correct manual link:

The suggested links would then be shown in a block in the top section of the question, like duplicate links.

Also, the amount of reputation earnable from these trivial questions is appalling. I'm sure a great portion of most high-rep users' points (including mine) is from answering "what was that function for replacing a string again?" type questions. This dilutes the value of reputation as a measure of true expertise a great deal.

I would suggest that answers to questions that get closed as "general reference" are made community wiki retroactively, taking away any reputation earned.

There is a certain amount of questions that are absolutely trivial in nature: How to format a date, how to concatenate a string, et cetera. Questions that could be solved by taking a look into the manual.

Random examples from the tags I frequent:

What those OPs need is a link to the right manual, which we should give them. But the question serves no purpose. They don't even have a use by being searchable, because any sane search query would lead to the actual manual as the first hit.

Jeff discusses the possibility of introducing a new close reason for this over at Scifi.stackexchange.com. According to Robert's suggestion there, it could go like this:

general reference: this question is too basic; the answer is indexed in any number of general internet reference sources designed specifically to find that type of information.

Please please implement this.

Add a field (like the "enter duplicate ID here" popup) for users to suggest the correct manual link:

The suggested links would then be shown in a block in the top section of the question, like duplicate links.

Also, the amount of reputation earnable from these trivial questions is appalling. I'm sure a great portion of most high-rep users' points (including mine) is from answering "what was that function for replacing a string again?" type questions. This dilutes the value of reputation as a measure of true expertise a great deal.

I would suggest that answers to questions that get closed as "general reference" are made community wiki retroactively, taking away any reputation earned.

replaced http://meta.scifi.stackexchange.com/ with https://scifi.meta.stackexchange.com/
Source Link

There is a certain amount of questions that are absolutely trivial in nature: How to format a date, how to concatenate a string, et cetera. Questions that could be solved by taking a look into the manual.

Random examples from the tags I frequent:

What those OPs need is a link to the right manual, which we should give them. But the question serves no purpose. They don't even have a use by being searchable, because any sane search query would lead to the actual manual as the first hit.

Jeff discusses the possibility of introducing a new close reason for this over at Scifi.stackexchange.com.Scifi.stackexchange.com. According to Robert's suggestion there, it could go like this:

general reference: this question is too basic; the answer is indexed in any number of general internet reference sources designed specifically to find that type of information.

Please please implement this.

Add a field (like the "enter duplicate ID here" popup) for users to suggest the correct manual link:

The suggested links would then be shown in a block in the top section of the question, like duplicate links.

Also, the amount of reputation earnable from these trivial questions is appalling. I'm sure a great portion of most high-rep users' points (including mine) is from answering "what was that function for replacing a string again?" type questions. This dilutes the value of reputation as a measure of true expertise a great deal.

I would suggest that answers to questions that get closed as "general reference" are made community wiki retroactively, taking away any reputation earned.

There is a certain amount of questions that are absolutely trivial in nature: How to format a date, how to concatenate a string, et cetera. Questions that could be solved by taking a look into the manual.

Random examples from the tags I frequent:

What those OPs need is a link to the right manual, which we should give them. But the question serves no purpose. They don't even have a use by being searchable, because any sane search query would lead to the actual manual as the first hit.

Jeff discusses the possibility of introducing a new close reason for this over at Scifi.stackexchange.com. According to Robert's suggestion there, it could go like this:

general reference: this question is too basic; the answer is indexed in any number of general internet reference sources designed specifically to find that type of information.

Please please implement this.

Add a field (like the "enter duplicate ID here" popup) for users to suggest the correct manual link:

The suggested links would then be shown in a block in the top section of the question, like duplicate links.

Also, the amount of reputation earnable from these trivial questions is appalling. I'm sure a great portion of most high-rep users' points (including mine) is from answering "what was that function for replacing a string again?" type questions. This dilutes the value of reputation as a measure of true expertise a great deal.

I would suggest that answers to questions that get closed as "general reference" are made community wiki retroactively, taking away any reputation earned.

There is a certain amount of questions that are absolutely trivial in nature: How to format a date, how to concatenate a string, et cetera. Questions that could be solved by taking a look into the manual.

Random examples from the tags I frequent:

What those OPs need is a link to the right manual, which we should give them. But the question serves no purpose. They don't even have a use by being searchable, because any sane search query would lead to the actual manual as the first hit.

Jeff discusses the possibility of introducing a new close reason for this over at Scifi.stackexchange.com. According to Robert's suggestion there, it could go like this:

general reference: this question is too basic; the answer is indexed in any number of general internet reference sources designed specifically to find that type of information.

Please please implement this.

Add a field (like the "enter duplicate ID here" popup) for users to suggest the correct manual link:

The suggested links would then be shown in a block in the top section of the question, like duplicate links.

Also, the amount of reputation earnable from these trivial questions is appalling. I'm sure a great portion of most high-rep users' points (including mine) is from answering "what was that function for replacing a string again?" type questions. This dilutes the value of reputation as a measure of true expertise a great deal.

I would suggest that answers to questions that get closed as "general reference" are made community wiki retroactively, taking away any reputation earned.

edited tags
Link
edited tags
Link
Jeff Atwood
  • 310.6k
  • 107
  • 887
  • 1.2k
Loading
added 87 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 93 characters in body
Source Link
user159834
user159834
Loading
added 67 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 68 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added link to exemplary question
Source Link
user159834
user159834
Loading
added 74 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 64 characters in body; Post Made Community Wiki
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 182 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
removed spurious [1] and the stupid "enter image description here"
Source Link
Loading
added 85 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
deleted 47 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 4 characters in body; added 32 characters in body; deleted 17 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 80 characters in body; added 113 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 48 characters in body; added 14 characters in body; added 204 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 66 characters in body; added 9 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 34 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 141 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
added 497 characters in body; deleted 889 characters in body; added 19 characters in body; added 37 characters in body
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading
Source Link
Pekka
  • 114.2k
  • 70
  • 387
  • 639
Loading