Skip to main content
Server Fault

Return to Answer

added 91 characters in body
Source Link
HBruijn Mod
HBruijn Mod
  • 82.5k
  • 25
  • 41

You may not ask many questions, but you write a lot of answers.

I would expect that you can write a question that is well received with a similar amount of effort as compared to what a good answer takes. (As long as you don't count all the frustrating time you spent on researching your problem before you admitted defeat and decided on asking for help here.)

Sometimes that will only be 5 minutes.
Another time your problem may need a lot of polishing and detail to phrase it as a good question. But if you need many hours to write it, who will read it to conclusion and actually answer?

Quoted from: How do I ask a good question on Server Fault?

"Good questions are clear, concise, and complete."

They do not need to be long.

The highest voted questions of the last two weeks is this one. To me it looks like one that was written up in less than 10 minutes, but regardless it still hints at more than sufficient prior analyses to already have found the root of the actual performance problem and followed by a valid request for guidance on how to address that.

You may not ask many questions, but you write a lot of answers.

I would expect that you can write a question that is well received with a similar amount of effort as compared to what a good answer takes. (As long as you don't count all the frustrating time you spent on researching your problem before you admitted defeat and decided on asking for help here.)

Sometimes that will only be 5 minutes.
Another time your problem may need a lot of polishing and detail to phrase it as a good question.

Quoted from: How do I ask a good question on Server Fault?

"Good questions are clear, concise, and complete."

They do not need to be long.

The highest voted questions of the last two weeks is this one. To me it looks like one that was written up in less than 10 minutes, but regardless it still hints at more than sufficient prior analyses to already have found the root of the actual performance problem and followed by a valid request for guidance on how to address that.

You may not ask many questions, but you write a lot of answers.

I would expect that you can write a question that is well received with a similar amount of effort as compared to what a good answer takes. (As long as you don't count all the frustrating time you spent on researching your problem before you admitted defeat and decided on asking for help here.)

Sometimes that will only be 5 minutes.
Another time your problem may need a lot of polishing and detail to phrase it as a good question. But if you need many hours to write it, who will read it to conclusion and actually answer?

Quoted from: How do I ask a good question on Server Fault?

"Good questions are clear, concise, and complete."

They do not need to be long.

The highest voted questions of the last two weeks is this one. To me it looks like one that was written up in less than 10 minutes, but regardless it still hints at more than sufficient prior analyses to already have found the root of the actual performance problem and followed by a valid request for guidance on how to address that.

Source Link
HBruijn Mod
HBruijn Mod
  • 82.5k
  • 25
  • 41

You may not ask many questions, but you write a lot of answers.

I would expect that you can write a question that is well received with a similar amount of effort as compared to what a good answer takes. (As long as you don't count all the frustrating time you spent on researching your problem before you admitted defeat and decided on asking for help here.)

Sometimes that will only be 5 minutes.
Another time your problem may need a lot of polishing and detail to phrase it as a good question.

Quoted from: How do I ask a good question on Server Fault?

"Good questions are clear, concise, and complete."

They do not need to be long.

The highest voted questions of the last two weeks is this one. To me it looks like one that was written up in less than 10 minutes, but regardless it still hints at more than sufficient prior analyses to already have found the root of the actual performance problem and followed by a valid request for guidance on how to address that.