Skip to main content

Return to Answer

Post Timeline

Grammar
Source Link
Sebastian Simon
Sebastian Simon
  • 19.8k
  • 5
  • 24
  • 29

You have a lot of code there. I wouldn't expect most of that to be necessary to reproduce your problem. Remove as much of it as you can while still having an example that reproduces your problem.

Then with your explanation, remove as much as you can get away with. If it's not giving me useful information that I would need to create an answer, omit it. Also make a point of having the most important information, and your main problem statement, as early in the question as possible. I shouldn't have to read the the whole thing to know what your core problem is. Your problem should be clear from the first few sentences, with the rest just being "the nitty gritty details" that it takes to actually write a full solution.

You have a lot of code there. I wouldn't expect most of that to be necessary to reproduce your problem. Remove as much of it as you can while still having an example that reproduces your problem.

Then with your explanation, remove as much as you can get away with. If it's not giving me useful information that I would need to create an answer, omit it. Also make a point of having the most important information, and your main problem statement, as early in the question as possible. I shouldn't have to read the the whole thing to know what your core problem. Your problem should be clear from the first few sentences, with the rest just being "the nitty gritty details" that it takes to actually write a full solution.

You have a lot of code there. I wouldn't expect most of that to be necessary to reproduce your problem. Remove as much of it as you can while still having an example that reproduces your problem.

Then with your explanation, remove as much as you can get away with. If it's not giving me useful information that I would need to create an answer, omit it. Also make a point of having the most important information, and your main problem statement, as early in the question as possible. I shouldn't have to read the whole thing to know what your core problem is. Your problem should be clear from the first few sentences, with the rest just being "the nitty gritty details" that it takes to actually write a full solution.

Source Link
Servy
Servy
  • 203.8k
  • 105
  • 686
  • 809

You have a lot of code there. I wouldn't expect most of that to be necessary to reproduce your problem. Remove as much of it as you can while still having an example that reproduces your problem.

Then with your explanation, remove as much as you can get away with. If it's not giving me useful information that I would need to create an answer, omit it. Also make a point of having the most important information, and your main problem statement, as early in the question as possible. I shouldn't have to read the the whole thing to know what your core problem. Your problem should be clear from the first few sentences, with the rest just being "the nitty gritty details" that it takes to actually write a full solution.