But sometimes I think you're too hard on yourself (and others) on this issue. If it turns out that your question isn't as insightful as you'd hoped or if it turns out that it's not as hard as you expected, I don't think there's any reason to close (or convert to wiki). In the question you asked two days ago, it looked like you converted to wiki and voted to close (I'm not certain it's your vote to close) when Emerton pointed out that the answer you accepted was fairly standard. One of the things MO is really great for is questions that somebody else knows the answer to right away. There's nothing wrong with not realizing that some standard result applies to your situation. Then again, maybe I'm biased because I answered that question, or maybe I misunderstood what happened.
]]>I do disagree with Anton (and presumably with many other users of MathOverflow) regarding the ease at which a question may be formulated. Asking good, insightful questions is not an easy task. If it were, then science and mathematics would be a lot easier than they are. I try to foster this in my students by making them turn in 3x5 index cards with questions on them (one per class) that are graded. I also employ the Socratic method, even in pure math classes. Asking good questions takes experience, perseverance, and frequently assistance (i.e. it often takes a group to develop the best questions).
Actually, I think we agree on that. As it says at the top of the How to Ask page, "Using Math Overflow should be an extension of the way you normally do mathematics, and the same rules you use to effectively solve problems can be used to make good MO questions. Just like solving problems, crafting good questions requires you to put in some effort!"
I'm not completely sure what you're referring to when you say that I've said it's easy to formulate a question. I think I have said that it should be relatively easy to remove vagueness from your written question, assuming you really have a concrete question you're trying to answer. If you come to MO thinking, "I'm frustrated by elliptic curves; I'd like somebody to straighten me out" then you can expect to have trouble. You're looking to have a discussion, which is fine, but it just won't work well on MO. Getting from general confusion to a concrete question can be tough, and that's something you pretty much have to do before you come to MO. This step requires effort; nobody on MO can do it for you and you absolutely cannot skip it. The concrete question you come up with may just be the first step to resolving your confusion and it may be pretty broad, but it has to have a specific goal. It has to be possible to explain your question to somebody else so that they know what an answer would look like.
Once you have a question, it might still be hard to express it really well, but you should be able to "put all your cards on the table." If it turns out that you left something out or that there are multiple ways to interpret your question, you should be able to fill the gap or resolve the ambiguity without much difficulty. If you can't, then you probably came to MO too early in your problem-solving work flow and you should be mildly embarrassed. Following the advice in the How to Ask page should prevent these embarrassing situations where you don't really have a focused question or you're trying to ask too many questions at once.
]]>My other disappointment is with the reputation/voting/closing system. While I think its intent was ultimately good, in practice it seems to foster too much animosity. It's too divisive in practice.
I do disagree with Anton (and presumably with many other users of MathOverflow) regarding the ease at which a question may be formulated. Asking good, insightful questions is not an easy task. If it were, then science and mathematics would be a lot easier than they are. I try to foster this in my students by making them turn in 3x5 index cards with questions on them (one per class) that are graded. I also employ the Socratic method, even in pure math classes. Asking good questions takes experience, perseverance, and frequently assistance (i.e. it often takes a group to develop the best questions).
]]>consider a professional mathematician, i.e., a university professor. Say they are not at a top school and they don't study algebraic geometry or a related field. What is the likelihood that they will ask a question here when they know that there is some not small chance that they will be ignored or get a beating for it?
I think I fall into this category, thus providing a case study for your speculative thought. I admit to having asked only two questions; one was actually related to algebraic geometry, and got some good answers. The other was from PDE theory, and has so far received no answers – most likely because there are hardly any PDE people here. Do I feel ignored? Yes, a little, but I realize that nobody has an obligation to take an interest in a question waaay outside their own field, so it doesn't bother me. Have I received a beating for it? Not at all, and it would have been a tremendous surprise if i did. If I have a problem on MO, it's just that gathering reputation is taking a lot of time, because my interests don't match those of the majority here very well. (But is that a problem really? No, reputation only results in higher powers which implies some sort of obligation, and being without could be considered a boon.) In short, I wouldn't worry too much about the treatment of hypothetical professors from second-rate universities.
]]>I agree that it's not always necessary to close a question if it needs to be improved, but sometimes it is. One rule I use for vague questions is, "if any answer would have to start of with a guess of what the question actually is, the question should be closed." That's a situation where I think allowing answers to accumulate is actually harmful. This is the reason I voted to close the limsup liminf question, though it turns out my assessment was off.
]]>By the way, if you have >2000 reputation and you think you can improve a closed question without seriously distorting the meaning of the OP, do it! If you're lacking some information, so you can't improve the question without changing the meaning significantly, think about what the OP would need to do to improve the question and ask them to do exactly that. Perhaps link to some part of the How to Ask page. If there's something you wish were in the How to Ask page so that you wouldn't have to repeat the same thing all over the site, tell me and I'll add it.
]]>More generally, I think we as a community will have to change our understanding of what it means to close a question. As more people break the 3k reputation boundary, this will become more and more important. Right now, I think many people think it means that the question is totally hopeless and shouldn't ever have been asked. Closing a question should usually mean something closer to, "this question should be (temporarily?) taken out of circulation for some reason." Typically, this means that the asker needs to clarify the terms, the motivation, or the question itself. I don't see what's wrong with voting to close a question for these reasons, even if the question is outside your area of expertise. But I do think you should leave (or vote up) a comment explaining what's wrong with the question and how it can be improved and reopened (if it is indeed salvageable). This is exactly why you can still edit a closed question and why an edit bumps the question to the top of the home page, so that people can re-evaluate the question and vote to reopen if appropriate.
]]>