3 ms·
This kind of thinking is exactly why I stopped asking questions on SO a long time ago. Because once you can construct the perfect question, you can most certai
by haspok 3y ago
This kind of thinking is exactly why I stopped asking questions on SO a long time ago.
Because once you can construct the perfect question, you can most certainly answer it yourself. It should be OK for questions to be somewhat vague, to contain "noise" and non-related stuff (because how on earth should the person asking the question know if something is relevent if they don't know the solution already?).
And I think in most cases a "complete minimal failing example" is way overkill. If someone in the future runs into the same problem, they have code already, and if there is already a solution accepted, then all that is needed is the description of the problem case and the solution (and in the best case, a root cause analysis, but that is an optional extra).
Some mods seem to think that SO is the next Encyclopedia Britannica, and each question is an article in it. This was not true in the beginning, and I don't feel like this is the right direction. But who cares about what I think.
- kqr 3y ago> Because once you can construct the perfect question, you can most certainly answer it yourself. Not if what you're lacking is declarative knowledge, which is what the site tries to elicit, to a first approximation anyway. You should reduce the question to the point where you can say "between substeps 1.3.5 and 1.3.6 there seems to be a proposition I don't know. What is it?" If you can't reduce the problem to a missing proposition, there are better resources to turn to for help with debugging it step-by-step until you have isolated a problem. I've had success with mentoring and IRC.