Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

It is unfortunate that questions like this were allowed to stay open (and got 5 UVs). It's great that someone received an answer ...but if that question had been asked today, it would have been railed to the coffin if the OP hadn't supplied evidence of previous attempts for resolution.

What is most damaging is the precedent ...if a new user comes along and sees this question, that person will believe that someone will write their entire solution. The notion of show me teh codez is not acceptable.

Asking for a way to increase the awareness of unacceptable questions is futile. I simply do not feel there is anything more we can reasonably accomplish. We have a good team of moderators, editors and reviewers.

But to the problem of questions like this that slipped through the cracks, how can we improve it's quality? Should it be closed? Locked with an explanation?

share|improve this question
Just vote to close it, same as you would today. Downvote, too, if you feel it's appropriate. – Cody Gray Apr 2 '13 at 23:52
It needed editing, so I did that. It's not the greatest question, but it got a good answer. – Lance Roberts Apr 3 '13 at 0:07
+1. You have a good point - it's a corner case where many people find it very useful even though the OP took no part in that. – djechlin Apr 3 '13 at 0:50
@CodyGray close no, DV yes. "Shows no research effort" but is a very clear, constructive and evidently useful question. – djechlin Apr 3 '13 at 0:50
+1 for the self-referential question title (although probably unintended!). – JBentley Apr 3 '13 at 1:24

Huh... That question's had 21 thousand views. I'm not sure you can say it "fell through the cracks", given the average view count for questions asked in '09 is 2.8K.

In addition to the up-votes, 8 anonymous users have marked it helpful (one marked it unhelpful), with the answer getting 6 and 3 helpful/unhelpful anonymous votes respectively.

That's not a lot of feedback, particularly given the number of views. If it really bugs you, you could down-vote it and reduce the score by 20%. Think about that.

Or don't. The guy asked a simple question, got a simple answer that satisfied him, and long ago moved on. Who cares?

share|improve this answer
I'll agree it has good stats. The point is that the question, if asked today, would have been closed in 5 minutes. It also sets the example that this is an okay question to ask and sets a new user up for failure. – IAbstract Apr 3 '13 at 0:45
You mean like this one? Not all "howto" questions get closed, @IAbstract. Some of them even get decent answers. After all this time, there's still no "didn't post wall of code" close reason. As much as lazy questions bug me, I'd be more concerned if specific questions with specific answers were getting closed just for the hell of it; there's nothing necessarily wrong with a simple question. – Shog9 Apr 3 '13 at 0:56
If we're going to add a "wall of code" close reason, let's start with "did post a wall of code". – Cody Gray Apr 3 '13 at 4:06
@Shog9: I don't understand why you think I expect a wall of code. The expectation is that we simply see some effort. Granted, not all questions require code. But the question I pointed out is nothing more than show me the code. – IAbstract Apr 3 '13 at 13:07

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .