Skip to main content
Commonmark migration
Source Link

#Why is requesting documentation better than asking it as a question on Stack Overflow?

Why is requesting documentation better than asking it as a question on Stack Overflow?

Don't get me wrong. I like the idea of that Stackumentation, but as far I understood it, documentation seems to be good when someone asks for it. Writing documentation takes much longer than writing an answer to a question on Stack Overflow. IMHO, most users want a fast answer which solves their problem as soon as possible. What is the advantage for the user to ask for it?

#Will a documentation request get a review or a vote limit before starting documentation?

Will a documentation request get a review or a vote limit before starting documentation?

I can imagine some cases where documentation can be pointless:

  • A user don't understand the documentation and asks for a new one.
    I see here two options:

    1. Document it anyway since it might help others
    2. Just help that user with a simple explanation
  • A user doesn't find the documentation because she or he uses a blob without documentation.

Possible solutions:

  1. We could give hints on how to improve the Google skills to find the documentation
  2. Document it just because Stack Overflow has a better search rank than the original documentation or other helpful resources

Both problems might be solvable with a limit before starting the documentation or a review, so that pointless requests won't trigger a creation of a documentation. What do you think about it?

#Why is requesting documentation better than asking it as a question on Stack Overflow?

Don't get me wrong. I like the idea of that Stackumentation, but as far I understood it, documentation seems to be good when someone asks for it. Writing documentation takes much longer than writing an answer to a question on Stack Overflow. IMHO, most users want a fast answer which solves their problem as soon as possible. What is the advantage for the user to ask for it?

#Will a documentation request get a review or a vote limit before starting documentation?

I can imagine some cases where documentation can be pointless:

  • A user don't understand the documentation and asks for a new one.
    I see here two options:

    1. Document it anyway since it might help others
    2. Just help that user with a simple explanation
  • A user doesn't find the documentation because she or he uses a blob without documentation.

Possible solutions:

  1. We could give hints on how to improve the Google skills to find the documentation
  2. Document it just because Stack Overflow has a better search rank than the original documentation or other helpful resources

Both problems might be solvable with a limit before starting the documentation or a review, so that pointless requests won't trigger a creation of a documentation. What do you think about it?

Why is requesting documentation better than asking it as a question on Stack Overflow?

Don't get me wrong. I like the idea of that Stackumentation, but as far I understood it, documentation seems to be good when someone asks for it. Writing documentation takes much longer than writing an answer to a question on Stack Overflow. IMHO, most users want a fast answer which solves their problem as soon as possible. What is the advantage for the user to ask for it?

Will a documentation request get a review or a vote limit before starting documentation?

I can imagine some cases where documentation can be pointless:

  • A user don't understand the documentation and asks for a new one.
    I see here two options:

    1. Document it anyway since it might help others
    2. Just help that user with a simple explanation
  • A user doesn't find the documentation because she or he uses a blob without documentation.

Possible solutions:

  1. We could give hints on how to improve the Google skills to find the documentation
  2. Document it just because Stack Overflow has a better search rank than the original documentation or other helpful resources

Both problems might be solvable with a limit before starting the documentation or a review, so that pointless requests won't trigger a creation of a documentation. What do you think about it?

Copy edited. Used the official name of Stack Overflow - see section "Proper Use of the Stack Exchange Name" in http://stackoverflow.com/legal/trademark-guidance (the last section).
Source Link
Peter Mortensen
  • 31.2k
  • 4
  • 24
  • 14

#Why is requesting a documentation better than asking it as a question on StackOverflowStack Overflow?

Don't get me wrong. I like the idea of that Stackumentation, but as far I understood it, a documentation seems to be good when someone asks for it. Writing a documentation takes much longer than writing an answer to a question on StackOverflowStack Overflow. IMHO the, most users want a fast answer which solves their problem as soon as possible. What is the advantage for the user to ask for it?

#Does#Will a documentation requests willrequest get a review or a vote limit before starting documentation?

I can imagine some cases where a documentation can be pointless:

  • A user don't understand the documentation and asks for a new one.
      
    I see here two options:

    1. Document it anyway since it might help others
    2. Just help that user with a simple explanation
  • A user doesn't find the documentation because she or he uses a blob without documentation. Possible solutions:

Possible solutions:

  1. We could give hints on how to to improve the Google skills to find the documentation
  2. Document it just because StackOverflowStack Overflow has a better search rank than the original documentation or other helpful resources

Both problems might be solvable with a limit before starting the documentation or a review, so that pointless requests won't trigger a creation of a documentation. What do you think about it?

#Why is requesting a documentation better than asking it as question on StackOverflow?

Don't get me wrong. I like the idea of that Stackumentation, but as far I understood it, a documentation seems to be good when someone asks for it. Writing a documentation takes much longer than writing an answer to a question on StackOverflow. IMHO the most users want a fast answer which solves their problem as soon as possible. What is the advantage for the user to ask for it?

#Does a documentation requests will get a review or a vote limit before starting documentation?

I can imagine some cases where a documentation can be pointless:

  • A user don't understand the documentation and asks for a new one.
      I see here two options:

    1. Document it anyway since it might help others
    2. Just help that user with a simple explanation
  • A user doesn't find the documentation because she or he uses a blob without documentation. Possible solutions:

  1. We could give hints on how to to improve the Google skills to find the documentation
  2. Document it just because StackOverflow has a better search rank than the original documentation or other helpful resources

Both problems might be solvable with a limit before starting the documentation or a review, so that pointless requests won't trigger a creation of a documentation. What do you think about it?

#Why is requesting documentation better than asking it as a question on Stack Overflow?

Don't get me wrong. I like the idea of that Stackumentation, but as far I understood it, documentation seems to be good when someone asks for it. Writing documentation takes much longer than writing an answer to a question on Stack Overflow. IMHO, most users want a fast answer which solves their problem as soon as possible. What is the advantage for the user to ask for it?

#Will a documentation request get a review or a vote limit before starting documentation?

I can imagine some cases where documentation can be pointless:

  • A user don't understand the documentation and asks for a new one. 
    I see here two options:

    1. Document it anyway since it might help others
    2. Just help that user with a simple explanation
  • A user doesn't find the documentation because she or he uses a blob without documentation.

Possible solutions:

  1. We could give hints on how to improve the Google skills to find the documentation
  2. Document it just because Stack Overflow has a better search rank than the original documentation or other helpful resources

Both problems might be solvable with a limit before starting the documentation or a review, so that pointless requests won't trigger a creation of a documentation. What do you think about it?

grammar improvements
Source Link
sampathsris
  • 22.4k
  • 5
  • 27
  • 38

#Why is requesting a documentation better thenthan asking it as question on StackOverflow? Don't

Don't get me wrong. I like the idea of that Stackumentation, but as far I understood it, a documentation seems to be good when someone asks for it. Writing a documentation takes much longer thenthan writing an answer to a question on StackOverflow. IMHO the most users want a fast answer which solves their problem as soon as possible. What is the advantage for the user to ask for it?

#Does a documentation requests will get a review or a vote limit before starting documentation? I

I can imagine some cases where a documentation can be pointless:

  • A user don't understand the documentation and asks for a new one.
    I see here two options:

    1. Document it anyway since it might help others
    2. Just help that user with a simple explanation
  • A user doesn't find the documentation because she or he uses a blob without documentation.
      Possible solutions:

  1. We might cancould give hints on how to to improve the Google skills to find the documentation
  2. Document it just because StackOverflow has a better search rank thenthan the original documentation or other helpful resources

Both problems might beenbe solvable with a limit before starting the documentation or a review, so that pointless requests won't trigger a creation of a documentation. What do you think about it?

#Why is requesting a documentation better then asking it as question on StackOverflow? Don't get me wrong I like the idea of that Stackumentation, but as far I understood it a documentation seems to be good when someone asks for it. Writing a documentation takes much longer then writing an answer to a question on StackOverflow. IMHO the most users want a fast answer which solves their problem as soon as possible. What is the advantage for the user to ask for it?

#Does a documentation requests will get a review or a vote limit before starting documentation? I can imagine some cases where a documentation can be pointless:

  • A user don't understand the documentation and asks for a new one.
    I see here two options:

    1. Document it anyway since it might help others
    2. Just help that user with a simple explanation
  • A user doesn't find the documentation because she or he uses a blob without documentation.
      Possible solutions:

  1. We might can give hints how to to improve the Google skills to find the documentation
  2. Document it just because StackOverflow has a better search rank then the original documentation or other helpful resources

Both might been solvable with a limit before starting the documentation or a review, so that pointless requests won't trigger a creation of a documentation. What do you think about it?

#Why is requesting a documentation better than asking it as question on StackOverflow?

Don't get me wrong. I like the idea of that Stackumentation, but as far I understood it, a documentation seems to be good when someone asks for it. Writing a documentation takes much longer than writing an answer to a question on StackOverflow. IMHO the most users want a fast answer which solves their problem as soon as possible. What is the advantage for the user to ask for it?

#Does a documentation requests will get a review or a vote limit before starting documentation?

I can imagine some cases where a documentation can be pointless:

  • A user don't understand the documentation and asks for a new one.
    I see here two options:

    1. Document it anyway since it might help others
    2. Just help that user with a simple explanation
  • A user doesn't find the documentation because she or he uses a blob without documentation. Possible solutions:

  1. We could give hints on how to to improve the Google skills to find the documentation
  2. Document it just because StackOverflow has a better search rank than the original documentation or other helpful resources

Both problems might be solvable with a limit before starting the documentation or a review, so that pointless requests won't trigger a creation of a documentation. What do you think about it?

Source Link
rekire
  • 48.1k
  • 22
  • 27
Loading