2 added 569 characters in body
source | link

I like that @Shog9 is willing to visit this topic. I like his suggestion and am just putting forward some food for thought.

This close reason tends to be for help vampires. Specifically, the kind who asks too much of answers. Users cannot be expected to write a book explaining the background and history, a library to support whatever is being created, and a framework to do the creating all in one answer.

The thing is, there are users capable of all that, but it is unfair for them to labor for hours on end just to deliver it to someone who could have done it themselves with effort and time.

I like shog's suggestion because of its aims. It aims at making askers be clear through explaining the why, what, and how of their question. Perhaps the message to accomplish those goals can be a little more clear.

Accomplishing the goal of this question is beyond the scope of a single answer. Questions should clearly explain a specific misunderstanding in its simplest form, how it was reached, and what was attempted to work through it.

Advantages:

  • Attempts to reduce the size of something new an answer must create. For example, "how do I create a div in jQuery" vs "how do I create a mobile app like facebook on Android"
  • Asks for an explanation of the misunderstanding the OP is facing while not asking for the entirety of what led to it
  • Asks for a simple backstory and for a sample attempt

Disadvantages:

  • References the "scope of a single answer" which is hard to determine
  • Uses the word misunderstanding which may not always be the best fit
  • Does not address code directly

I like that @Shog9 is willing to visit this topic. I like his suggestion and am just putting forward some food for thought.

This close reason tends to be for help vampires. Specifically, the kind who asks too much of answers. Users cannot be expected to write a book explaining the background and history, a library to support whatever is being created, and a framework to do the creating all in one answer.

The thing is, there are users capable of all that, but it is unfair for them to labor for hours on end just to deliver it to someone who could have done it themselves with effort and time.

I like shog's suggestion because of its aims. It aims at making askers be clear through explaining the why, what, and how of their question. Perhaps the message to accomplish those goals can be a little more clear.

Accomplishing the goal of this question is beyond the scope of a single answer. Questions should clearly explain a specific misunderstanding in its simplest form, how it was reached, and what was attempted to work through it.

I like that @Shog9 is willing to visit this topic. I like his suggestion and am just putting forward some food for thought.

This close reason tends to be for help vampires. Specifically, the kind who asks too much of answers. Users cannot be expected to write a book explaining the background and history, a library to support whatever is being created, and a framework to do the creating all in one answer.

The thing is, there are users capable of all that, but it is unfair for them to labor for hours on end just to deliver it to someone who could have done it themselves with effort and time.

I like shog's suggestion because of its aims. It aims at making askers be clear through explaining the why, what, and how of their question. Perhaps the message to accomplish those goals can be a little more clear.

Accomplishing the goal of this question is beyond the scope of a single answer. Questions should clearly explain a specific misunderstanding in its simplest form, how it was reached, and what was attempted to work through it.

Advantages:

  • Attempts to reduce the size of something new an answer must create. For example, "how do I create a div in jQuery" vs "how do I create a mobile app like facebook on Android"
  • Asks for an explanation of the misunderstanding the OP is facing while not asking for the entirety of what led to it
  • Asks for a simple backstory and for a sample attempt

Disadvantages:

  • References the "scope of a single answer" which is hard to determine
  • Uses the word misunderstanding which may not always be the best fit
  • Does not address code directly
1
source | link

I like that @Shog9 is willing to visit this topic. I like his suggestion and am just putting forward some food for thought.

This close reason tends to be for help vampires. Specifically, the kind who asks too much of answers. Users cannot be expected to write a book explaining the background and history, a library to support whatever is being created, and a framework to do the creating all in one answer.

The thing is, there are users capable of all that, but it is unfair for them to labor for hours on end just to deliver it to someone who could have done it themselves with effort and time.

I like shog's suggestion because of its aims. It aims at making askers be clear through explaining the why, what, and how of their question. Perhaps the message to accomplish those goals can be a little more clear.

Accomplishing the goal of this question is beyond the scope of a single answer. Questions should clearly explain a specific misunderstanding in its simplest form, how it was reached, and what was attempted to work through it.