Should Stack Exchange in general be awarding "A"s for Effort?

Question

This just came up again:

homework is not acceptable if the asker has made no effort whatsoever

I'm developing a bit of an involuntary twitch that manifests itself when I encounter the word "effort" on Stack Overflow these days.

Don't get me wrong — effort is good. At least, productive effort is good. But seeing the word thrown around so often without any qualifications makes me start to wonder if we're not becoming that teacher who punishes students for finishing their assignments too quickly by forcing them to sit motionless until the rest of the class has finished. That is, we're more concerned with seeing folks visibly struggle than we are with the results of their labors.

Surely the important goal here is the production of well-asked, well-answered questions, right? Not visible self-flagellation...

I've observed one other rather nasty manifestation of this attitude: folks flagging or voting to close straightforward "How can I do X using Y?" questions. These tend to crop up a lot when there is a new OS or API release, and when the documentation is lacking or incomplete they're often quite useful — but again, there seems to be this idea that because the asker didn't log 50 hours trying to re-invent the wheel first, the question is inappropriate — regardless of how clearly written or generally useful it is.

I was hoping to forestall this when we rolled out the new close reasons back in June, with off-topic reasons targeted specifically at poor quality questions asking for help debugging or writing code. "Describe a specific problem" they read, "Demonstrate a minimal understanding of the topic". I wrote those to mean, "tell us what you know, and what you need to know"...

...but every time I ask someone else to interpret them, I hear, "Oh, those are for questions that don't show enough effort".

I'm sorry, but... When I'm trying to solve a problem and searching for similar questions on Stack Overflow, I really don't care how much effort the asker demonstrates in his question. In fact, unless that effort translated directly into a clear, concise question that I can easily identify as being close to my own and then quickly scroll past to get to the answers, I'm rather resentful of ostentatious displays of effort.

Am I being crazy here? Selfish? Or are those of you throwing out "must demonstrate effort" left and right perhaps missing the point?

Answer 1

Surely the important goal here is the production of well-asked, well-answered questions, right? Not visible self-flagellation...

When I ask for effort, what I'm really looking for is a starting point, some context for where the problem actually exists. So many XY Questions are easily answered by seeing a code sample. Without that, it's like trying to diagnose engine trouble over the phone... even the expert Tappet brothers end up divided over the problem (much more the solution).

The average no-code-included question I see is so vague that nearly every answerer invents a completely different context into which they can inject their awesome knowledge. It's like a rorschach test... you see nails if you've got a hammer, or screws if you've got a screwdriver. Answering becomes a crapshoot... who can guess the OP's actual problem? In the meantime, considerable effort is expended in the comment sections of the question and answer trying to define the OP's actual situation (and what they want). This is effort that could have been used answering one or two other user's questions, had the question been asked clearly in the first place.

Basically, in my opinion, you can't have a well-asked question without some effort and, more often than not, some documentation of that effort.

folks flagging or voting to close straight-forward "How can I do X using Y?" questions. These tend to crop up a lot when there is a new OS or API release, and when the documentation is lacking or incomplete they're often quite useful

This is largely answered by the above, but a single statement by the OP to the effect of "I looked in the documentation [link] and can't find an adequate answer" will, in every case I've seen, result in upvotes and answers. Without that, every reader is forced to go look at the documentation themselves, wasting time and effort. Some just vote to close.

unless that effort translated directly into a clear, concise question that I can easily identify as being close to my own and then quickly scroll past to get to the answers, I'm rather resentful of ostentatious displays of effort.

I've seen plenty of questions which include long blocks of code in an attempt to display "effort". I agree that this is annoying, and I don't accept these as evidence of effort. To me, "effort" is defined as having worked intelligently toward a solution, not just brute exertion. Like target shooting, I'm not interested in someone who has blindly fired off 10 shots and nothing hit. I'm interested in someone who made the effort to line up the shot, but missed. That's someone I want to help.

More important than the worthiness of the asker, though, is the quality of the site as a whole. Asking the OP to show a minimal amount of work helps to produce clearer and more useful questions for other, future readers. Without some effort on the askers part, the site becomes cluttered with questions that are either simple, uninteresting duplicates; or questions that are so extremely specific as to be useless to other engineers. It is for the benefit of the site as a whole, as well as the OP, that we should be asking the OP to show us what they've tried and where they're stuck.

---

I'll also add that effort leads to much more interesting questions. If you make a habit of stopping and asking every time you meet the slightest resistance, your questions are not going to be very creative or well thought out. But if you are decent at what you do and have put in considerable effort to achieve some result and are still having trouble, well then by golly you may just have an awesome question. Awesome questions lead to lots of rep, high page views and, for Stack Overflow, increased ad revenue. That's good, right?

Answer 2

Shog, you're attacking a straw man here. You should know better than that.

Folks aren't looking for "effort" because they think displays of struggle are some sort of magic pixie dust, able to turn a terrible, useless question into gold. They're looking for effort because the lack thereof is the most blatantly obvious hallmark of the thousands of terrible, terrible questions asked every day on Stack Overflow.

• Lack of research effort leading to countless duplicates.
• Lack of effort describing the problem, leading to unclear and misleading questions.
• Lack of presentation effort, leading to hard to read questions.

When I pick a question at random off of the list of the newest, there's a pretty good chance that it sucks. And while I may not be able to describe what the author needs to do to fix it, I can sure as shootin' identify what he didn't do... and that all boils down to a lack of effort.

Maybe your lazy teacher just doesn't want to spend time grading yet another half-assed exam, and hopes that by forcing the student to sit there he'll be forced to put some more thought into his work purely for something to do...

Of course, as understandable though that may be, it's also naive. "Show more effort" is terrible guidance, as the number of questions with "effort" in the form of long, pointless code listings demonstrates. JDB nails it: we don't want to see "effort" so much as we want context!

Show your work

Geobits points out that a better analogy here are those "show your work" marks your teachers used to leave on your math homework.

When a good teacher imposes this requirement on his students, it's not about proving that they've put effort into the problems they've been asked to solve - it's to establish what they know so that he can teach them what they don't. Assuming your students understand the basic concepts involved is dangerous - if you're wrong, they may be too far behind to catch up by the time you find out. By showing their work, you're able to see exactly where they went wrong, and address the specific problem.

The same thing applies on Stack Overflow. And just as there are annoying, time-wasting teachers who demand to see long division next to the solutions to algebra problems, there are annoying people who demand to see "what you've tried" for questions where the only sane answer is "nothing, because I don't know what to try - that's why I'm asking!"

A minimal understanding

There's a famous interview with Richard Feynman, where he was asked the perfectly reasonable question, “how do two magnets attract or repel each other?” To which he responded,

I can't explain that attraction in terms of anything else that's familiar to you. For example, if we said the magnets attract like if rubber bands, I would be cheating you. Because they're not connected by rubber bands. I'd soon be in trouble. And secondly, if you were curious enough, you'd ask me why rubber bands tend to pull back together again, and I would end up explaining that in terms of electrical forces, which are the very things that I'm trying to use the rubber bands to explain. So I have cheated very badly, you see. So I am not going to be able to give you an answer to why magnets attract each other except to tell you that they do. And to tell you that that's one of the elements in the world - there are electrical forces, magnetic forces, gravitational forces, and others, and those are some of the parts. If you were a student, I could go further. I could tell you that the magnetic forces are related to the electrical forces very intimately, that the relationship between the gravity forces and electrical forces remains unknown, and so on. But I really can't do a good job, any job, of explaining magnetic force in terms of something else you're more familiar with, because I don't understand it in terms of anything else that you're more familiar with.

Without communicating what he already knows, the asker creates a prohibitively difficult task for the answerer... He must assume a certain level of knowledge in order to answer, but if he gets it wrong he will waste both his time and that of the reader. The preferable option is to assume that the asker knows nearly as much as himself, as this greatly reduces the amount of background information that must be conveyed - but if he does this and the asker returns confused, his efforts were wasted - and indeed, the more likely scenario is that the asker's knowledge is far less than his own, since otherwise he would've probably solved the problem on his own.

Therefore, it is best for everyone if the asker holds a minimal understanding of the problem domain when he asks his question. If I can assume, when encountering a question on changing fuel injectors, that you know how to use standard tools and take basic precautions around gasoline, I can provide a much more direct, useful answer - likewise, if you’re asking how to shuffle an array using C#, I should be able to assume that you know how to use the language itself, are familiar with the basics of the standard library, etc.

So, how does one identify an asker who lacks a minimal understanding? Well... First off, it requires that you have a minimal understanding of the topic. If you have zero knowledge of the subject matter, you're going to do a pretty poor job of identifying questions that experts on the topic will struggle to answer. Lots of folks ran face-first into this problem when trying to review questions in the close queue - if you don't filter the list down to topics where you have some knowledge, it becomes very difficult and frustrating to review them.

And so this is where your "minimal understanding" close reason, as nice as it sounds, falls apart: identifying effort is easy, but gauging understanding can be impossibly hard.

What do you know, and what do you need?

Going back to JDB's answer, there's a much more straighforward way to describe what we're looking for here. A reasonable question needs:

1. Context!
2. A clear statement of the problem!
3. An explanation for why the obvious solution (if one exists) didn't work.

This could be as simple as, "How can I do #2 in #1 when #3 is unavailable" or as elaborate as a multi-page back-story and code listing. As long as all the elements are present, it's an answerable question with at least the potential to be useful to others.

And what do you know... The venerable How To Ask page lays out these very same criteria:

Tell us what you found (on this site or elsewhere) and why it didn’t meet your needs. ... Be specific ... give us details and context

Indeed, the old "Not a Real Question" close reason captured these as well:

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form.

And Ilmari Karonen works his way around to the same conclusion, suggesting:

Questions ... should be based on real problems that you face, not on idle speculation, impossible hypotheticals or exercise problems with no relevance outside the classroom.

These are all great catch-all descriptions for this sort of question, with the caveat that they don't provide much in the way of specific guidance for the asker. But let's back away from close reasons for a minute... For all the attention it gets, closing is neither the most convenient, nor most effective way to handle these questions.

Strategies for handling low-quality questions

During all of the recent discussions surrounding the close queue backlog, something's been bothering me... A pretty big chunk of the backlog is taken up by questions flagged or voted on using this "minimal understanding" reason. That's not surprising in the least - but it's a horribly inefficient way of dealing with these questions. It takes 5 voters to close a question, and because some amount of subject knowledge is required to properly evaluate them finding the right voters is extra-difficult. Meanwhile, folks who interpret the reason as "no effort shown" are pushing more and more questions into the queue every day...

...If they just down-voted the questions, a privilege available to nearly everyone flagging them, they'd drop out of sight a lot faster.

As shocking as the notion that someone might get their work done for free is, that's not a particularly compelling reason to put a lot of effort into closing a question. And if we factor out the downvoting guidance ("This question does not show any research effort; it is unclear or not useful") from our close reasons, they could become considerably more straightforward.

The only question left then becomes: can we live without our super downvote?

Answer 3

Stack Overflow is going the way of Usenet.

No, I don't mean that the quality is going down. I mean that the moderation of questions on Stack Overflow is focusing more and more on the effort made by the asker to conform to the group norms, and less and less on the goal of “collectively increasing the sum total of good programming knowledge in the world”.

Stack Overflow sought out to “build a great library of canonical answers”. A key characteristic of Stack Exchange, which distinguishes it from other forms of knowledge sharing on the web such as discussion groups and blogs, is that its tidbits of knowledge are searchable. We don't bury gems in 100 pages-long threads. We don't tell people to search the web, 'cause I'm sure this was answered back in '09 (or at least we shouldn't), nor do we answer for the 43278th time: we close the question as a duplicate of the '09 question. We edit posts to make sure they stay up to date. If someone comes up with a better answer three years down the line, we tell them to share their knowledge on the existing question. It's the “Wikipedia of long tail questions” — the Wikipedia of the non-notable. And we filter questions: we only want the answerable ones, not “how long is a piece of string” or “should I wear the blue tie or the green tie”.

The answers… Stack Exchange is all about the answers. Questions are just an enabler. When you need to know something, you might search for a question, but the answers are what you're after.

And yet… asking a good question is hard. So we ask people to put effort in asking their question. We grant people brownie reputation points for asking, albeit half as much per upvote as for answers.

I've sometimes wondered if halving the reputation for questions had been the right decision. I find that writing an answer is for the most part straightforward: 1. understand the question; 2. gather the facts; 3. find a solution; 4. explain. Asking a question is less forgiving: did I provide all the necessary background? Am I stating all the relevant facts? Have I not bogged down the question in unnecessary detail? Am I targeting the right audience? Have I sufficiently oriented the question so that I won't get inapplicable answers, yet not so much that I'd drive off non-obvious solutions? Reputation should in principle be an incentive to write good questions, like it is an incentive to write good answers.

Then again, what do askers care about reputation? By and large, askers don't want reputation¹. They want answers. So maybe reputation isn't so important an incentive anyway. Score is, though — a high-scoring question is more likely to attract answerers, and thus answers.

However score isn't such a good indication of a good question. A good question must be answerable, and score doesn't really indicate this. Plenty of well-written questions are unanswerable — because they're too subjective, too broad, off-topic, etc. Fortunately we have another tool to judge questions: closing. Closing determines whether a question is answerable.

Closing is clearly of value to the community — it's what determines whether the topic calls for answers, for those slices of knowledge that the site is about. Answer score has an obvious use in showing the good answers from the bad. What about question score? Question score has two major effects:

• The effect on the asker: the votes on a question factor in the asker's reputation.
• The effect on the community: the score on a question determines to some extent how much attention it gets.

If the asker's goal is aligned with the community's, then all is well: the asker wants answers, so the asker wants attention, so the asker wants a high-scoring question. But often there's a drift. Upvotes on a question are seen as a reward, and downvotes are seen as a punishment. Put effort into the question, get an upvote. Show no effort, get a downvote.

Yet the amount of effort by the asker is not a good indication of a good question.

If I spend a week debugging a 1000-line piece of code, and post it on Stack Overflow in desperation, that's a lot of effort². I may show my analysis, explain all the investigation steps I've taken… and the result will still be an ad hoc exercise in finding the needle in a haystack, useless to anyone else because no one else has exactly my code. On the contrary, a copy-paste of a homework or book exercise is the epitome of laziness³ yet is likely to be useful to many — well-designed homework exercises teach something, and building a canonical repository of solutions to exercises would be in fact a worthwhile use of Stack Exchange.

I've written thousands of answers on Stack Exchange, and I don't think that my most useful answers correspond to the best questions. In fact, detailed, researched questions often have a frustrating trait — they're buried in details that turned out to be irrelevant, which makes them poor duplicate targets, which makes posting detailed, canonical answers a waste. The most useful question for a canonical answer is one that gets to the point quickly and doesn't meander into side issues.

Over time, when a poor question has a good answer, one of two things tend to happen. Either the question gets closed, which is a waste of a good answer; or the question is improved, and thereafter upvoted (because it's now good), and the correlation between its score and the effort by the original asker is lost. Closing the question is detrimental to the community: the right thing is to forget about judging the asker and judge only the question.

When closing starts to be about effort, this does the community a disservice. Voting on questions is supposed to be about effort; closing is supposed to be about answerability.

One of the custom close reasons on Stack Overflow is “Questions asking for code must demonstrate a minimal understanding of the problem being solved.” One of the custom close reasons on Security is “Questions asking us to break the security of a specific system for you are off-topic unless they demonstrate an understanding of the concepts involved and clearly identify a specific problem.” I like these close reasons: in essence, they say “if you're so out of your element that you wouldn't be able to understand the answer, let the grown-ups talk”. There's no point in answering when the asker, or future visitors with the same question, wouldn't benefit from the answer. Unfortunately, on Stack Overflow, the close reason is often interpreted as requiring effort from the asker. No, that's not it. The asker may be trying very hard just to post that question, but if he's too far out of his depth, the question is useless. Conversely, the asker may have spent 30 seconds asking how to undo a mistake, and yet it's such a common issue, and fairly easy to fix, that this tidbit of knowledge is widely useful.

On a forum, when you write an answer, you're helping the asker individually. You don't want to waste your time on a lazy, demanding asker. On Stack Exchange, you're helping everyone with the same question, now or in five years' time. In five years, the amount of effort shown by the asker will be utterly irrelevant. What will matter is how many other people have found your answer useful.

Effort is a terrible thing to factor into question closure.

The problem you discuss in your question is real, and worrying. By insisting on effort, the Stack Overflow community is moving away from the goal of building a canonical repository of answers, and more towards being a forum with peculiar habits. But the question in your title is not the right one. We shouldn't be basing so many judgements on effort. Effort is the wrong problem.

I read the first couple of paragraphs and skipped your rant. Are you going to propose solutions or what?

That's a tough one.

When I started participating on Stack Exchange, I didn't see much point in downvoting questions. Either a question was answerable, or it should be closed. If the question was well-written and interesting I'd upvote it. Then gradually I started to want to convey a message that this question is bad and you should be ashamed. Because, yes, there are plenty of bad questions — not merely off-topic or ill-suited for Stack Exchange but what the hell are you on. Downvote.

Yet I often face the duality of the question score. If a lazy, badly written, poorly researched original post leads to a great answer, the question should be improved. We should downvote the asker but upvote the thread. Does that mean we should downvote or upvote the question? This dichotomy is very common.

Sorry, I'm falling back into rambling mode. Ok, so despite not using regular expressions, we have two problems.

1. Our primary problem is to build a great library of canonical answers.
2. Our secondary problem is to keep a decent signal-to-noise ratio on the demand front.

To solve our primary problem, the score of a question must indicate how useful it is. To solve our secondary problem, the score of a question must indicate how much effort went into it. We're back to this: question scores can't make up their mind whether they're rating the thread or the asker.

If it was only for problem #1 then we could do away with question score. We could even go further and do away with question ownership. What matters is the answers, so the question should belong to the community! Edit, edit away. Make each question awesome.

However I don't think this is realistic. Answering is hard work, we can't answer everything, we need quality control.

We could separate the two scores: have a score for the original question (contributing to the asker's reputation), and a score for the current state of the question (contributing to the thread's rank in searches). But maintaining two scores would be awfully complex. These scores would start out identical and gradually diverge over time as the question is edited. This system would be too hard to understand.

So I don't have anything radical to propose. Let's stick with the statu quo, with the schizophrenic question score. It's not too bad as long as we remember to distinguish score from answerability. Effort is a big part of question score. But it should not leak into closing.

Closing is all about answerability. Closing isn't about the asker, it's about the community. “No effort” is not, should not be, must not be a reason to close.

Answering no-effort questions is not “awarding ‘A’s”. Answering is imparting knowledge to thousands of people, of which a measly one happened to ask the question.

Stack Overflow needs to stop worrying about effort and learn to love the answers.

¹ _{Answerers aren't always after reputation either, but I think they're pretty much universally after positive attention, whether this attention takes a numerical form or not.}
² _{I should cite an example at this point, but I'm sure you know what I'm talking about.}
³ _{Ok, not quite. It's trumped by a scan of a homework exercise.}

Answer 4

It's not about Effort. It's about Respect.

The line I draw for moderation is based on the probability someone will say, "Try X" and the OP will respond, "I already tried X". To which the person will inevitably comment, "Try Y" and the OP will then say, "But I already tried Y!" (without having it in their question originally).

It all comes down to respecting the time of people who answer. If a question doesn't show that respect, I'm more likely to downvote it or to close it. It's not about effort, it's about respect.

You can show almost no effort towards solving the problem yourself but if your question respects other people's time, it's fine.

Examples of questions that do not respect other people's time:

• "{{text of assignment}}: Need answer"
• "{{A and B}}: Benchmark this for me."
• Complete sum of problem is a vague, "It doesn't work. Tell me why."

An example of a Question that shows no effort but respect other people's time:

• "I'm trying to filter two properties in angular JS, the filter documentation (link to it) doesn't make it clear how to filter on a property. The example doesn't even show what I'm looking for. Using the following code ((text of code)), how do I filter on an inexact match of this property?"

Sometimes people conflate Effort with respect. Showing effort is one way to show respect, but certainly not the only way. Your original text of 'minimal understanding' comes close to what we're trying to get out of a user, but I feel like the text should actually say (something to the effect of):

Questions asked on Stack Overflow should respect other people's time. Showing respect is pretty easy: Take care to spell out your problem, use punctuation, format your code, and tell us exactly why something isn't working. Saying, "It's not working" without being more specific forces people to spend precious time they could be using to help you to get more information so they can help you. You don't need to spend hours trying to solve the problem yourself before coming to us, but we do ask that you write your question with other people's time in mind.

Answer 5

I would like to distinguish between effort in formulating the question and effort in solving the problem. When I want to kill a post, it is mostly for a lack of the former.

Answer 6

Unfortunately, a great many questions I see are simply:

"I copy/pasted some code from somewhere and it doesn't work - please give me working code"

It comes under a lot of guises, but it often boils down to this. The OP isn't interested in making any effort because he isn't interested in the problem - he just wants to finish so he can get paid and go home. I'm sure we've all encountered cases where OPs have actually become somewhat surly with others who are explaining the solution but refusing to provide working code samples.

Showing some effort doesn't even require a basic understanding of what you are trying to do. It could even be simply writing your question clearly, or explaining how you think something works, or merely saying, "I have no idea how X creates Y - can someone put me on the right track so I can follow up on my own?". "Showing some effort" is a little bit like Art - you know it when you see it.

Most (many? some?) of us here are interested in teaching and nurturing, not just providing free labor. When we ask the users to "show some effort", it is both to ensure ourselves that we have a willing learner, and to teach the OP the early steps of how to investigate the problem for himself.

My answer assumes, of course, that we aren't simply trying to make a giant repository of answers to every question. I'm in the wrong place if we are.

Answer 7

Quick point. This is a bad question with no research effort and does not show the slightest nugget of effort:

Convert int to string?

Should it be closed? It's been viewed nearly 100,000 times and is the first result in google when you search for convert int to string c#.

Questions with no effort can be very useful if someone else needs the same piece of information

---

So if bad questions can be useful (maybe) a duplicate of a bad question is really, really not useful.

This for me raises another point, I see a lot of bad questions that already have a perfectly good answer in the system. I also see people making a lot of points by reiterating the same answers to these questions over and over again.

And why not, the system rewards answering a duplicate but it does not reward finding the duplicate and flagging it as such?

Answer 8

Often, when people put a bit of additional effort into solving their problem before they come to SO, they will find the solution without even needing to ask, because the answer already exists somewhere else.

That's the kind of behavior we're trying to encourage. It, in theory, reduces our workload.

---

and the show more effort line that many people give is mostly talk anyway.

If a question is

• clear enough to understand
• concise enough to post a brief solution to
• and interesting enough for future users to take utility from

it will be well received, regardless of how much effort the poster actually has shown toward solving the problem himself.

Answer 9

I just wrote a long winded rant on the subject of minimal understanding/effort, deleted it and decided to go with this instead...

A good measure of effort in my opinion, is the "What have you tried?" test. I'm talking about the article not the snarky comment...

When you’re asked “what have you tried?”, it doesn’t mean “show me the code you’ve written, or piss off”. What you have to do is at least try to help yourself – and the trying is the important thing.

Not just for avoiding pissing off someone who would otherwise be willing to give freely of their valuable time to help you, but actually for your own development. Do it enough times and the number of questions you’ll actually have to ask will start to go down. You’ll also be in the position to help others (including me), and that way everybody wins.

So next time you’re considering asking a question, you’d better be ready with a convincing answer when you’re asked “What have you tried?”

If your answer amounts to “not a lot”, take my word for it: the next question you get back will be “then why should I help you?”

"Show your effort" or "Must demonstrate a minimal understanding" are just the next generation of "What have you tried?" They are born out of frustration and can be used either constructively or destructively. It's up to the community to decide which way to turn.

It really comes down to maintaining a reasonably helpful attitude while holding back the flood of people who probably shouldn't be helped.

Answer 10

For me, effort means an attempt to research/ solve the problem. It doesn't have to mean that the user spent an hour spinning his wheels.

Tell me why the google results don't work, or tell me that google didn't return anything.

In your case of new technology, the user should have looked at the docs. If there aren't any docs, then the user should state as much.

Why do I ask for effort? Questions a lot of times can be too broad. If the user has done something, it provides scope; it provides direction. It means I don't have to waste my time with things that they have already tried; it means I can see better what they are trying to do.

Answer 11

I've always thought that the point of "homework questions must show some effort" was simply to discourage people from copying and pasting (sometimes literally, sometimes by manually retyping) each and every exercise from their textbook or exercise sheet to Stack Exchange.

Sure, it's a real easy way to ask a lot of questions (and an even easier way to get your homework done), and typically the questions will even be on topic and interesting (because the teacher or textbook author tried to make them so). But it's not what the Stack Exchange network really should be for.

Of course, most people would consider it just fine to ask for help with the occasional tricky exercise that you can't solve. But people who only do that aren't really contributing anything useful or original to the community — they're just being help vampires.

---

Fundamentally, I think all the longstanding issues with homework questions arise from a complicated "impedance mismatch" between the Stack Exchange model on one hand, and the general idea of homework exercises on the other.

Basically, the Stack Exchange system is based on the idea of people helping each other solve practical problems they face in their daily life, and thereby building a useful repository of practical knowledge and generally making the world a better place. To quote the "What is Stack Exchange?" page (emphasis mine):

"We welcome questions that are clear and specific, representing real problems that you face; Stack Exchange is not the place for conversation, opinions, or socializing."

Homework questions, however, are not "real problems" in this sense — they're artificial, made-up problems designed to train your problem-solving skills. Answering such questions doesn't "make the Internet a better place"; the only people it helps are those asked to solve that particular homework exercise (and even then, the help may backfire in the long run, if they just use Stack Exchange as a substitute for actually learning to solve the problems themselves).

Part of the problem, however, is that, by design, good homework questions are interesting. They're the kind of questions that make people want to answer them, that make people think "Ooh, I know this one!" So those questions tend to easily get answers, even when they're actually so localized that they really have no practical use outside the classroom.

So we have a class of questions that are trivially easy to ask (because you just need to copy the question from elsewhere) and attract a lot of answers (and often, consequently, upvotes), but typically contribute next to no lasting value to the site, or to the Internet as a whole. It's no wonder some people don't like them.

And, of course, just to make things more complicated, not all homework questions are bad questions: some are in fact based on real problems one might face outside a classroom, and even if they aren't, they often (by design) demonstrate some practically relevant technique or principle that a good answer may bring to the foreground and generalize upon. So just saying "homework questions are bad, mmkay" doesn't really cut it — not all of them are bad, just many of them.

---

So, granting that demanding askers to "visibly struggle" in an effort to show effort isn't the answer, what should we do about copy-and-paste homework questions?

My modest proposal would be to add a new closing reason (or perhaps replace one of the existing reasons) to reflect the wording I highlighted above, something like:

"not a real problem

Questions on [site] should be based on real problems that you face, not on idle speculation, impossible hypotheticals or exercise problems with no relevance outside the classroom."

Or perhaps it might be better to focus on the "copy-and-paste" rather than the "homework" aspect, and close them with:

"verbatim copy

Questions asked here must be original and based on real problems that you face, not copied verbatim from other sources (including textbooks, exercise sheets or other websites). If you wish to ask about a specific aspect of a problem presented elsewhere, please explain in your own words how the problem matters to you and what parts of it you need help with."

(I'm not entirely happy about that last sentence: it feels too long, and still doesn't fully communicate what I wanted to get at, which is that "I saw this problem elsewhere and can almost solve it, except for..." or "I saw this asked before, but I don't think the answers are right, because..." are generally OK, whereas "I got this for homework, please solve it for me!" isn't. But it's a start.)

Edit: Struck out the "not a real problem" suggestion above. As noted in the comments below, it's been tried and it didn't work well. I do still think there might be some merit to the "verbatim copy" close reason, as it more specifically focuses on the minimal-effort "Here's my homework, do it for me!" questions we don't really want. Besides, a lot of the really verbatim copy-pasted questions are probably somewhat iffy even on just copyright grounds alone.

Answer 12

For me the real meaning of the Demonstrate a minimal understanding of the topic close reason is:

This person did not show any effort of making the question readable, useful whatsoever. That is the real problem.

If someone does not provide code that's not the end of the world. But being just lazy and not caring should be closed. Often others need to ask for clarification, format the question, tags, correct grammar ...

Show some effort of making a good question for future visitors too, then all is fine.

Answer 13

I'm sorry, but... When I'm trying to solve a problem and searching for similar questions on Stack Overflow, I really don't care how much effort the asker demonstrates in his question. (...) I'm rather resentful of ostentatious displays of effort.

You're fighting a strawman.

Most of these low quality questions display no effort whatsoever: the information is a simple Google away -- more often than not on this very site, at that. Sites like "Let me google that for you" may pass off as rude and get rejected, but they'd be a perfect fit for scores of questions asked on SO.

Also, the threshold is extremely low. Something as simple as "my problem is different from this other SO question" or "The doc [link] is unclear" demonstrates enough effort (i.e. OP used Google) and attracts upvotes and answers.

Here's a different suggestion: add a "I have googled my question" checkbox on the form that allows to ask a question. If left unchecked, submit the question to google in a new tab when the form is submitted.

Answer 14

I believe "How can I do X using Y?" should have their place on Stack Overflow. Many times a user tries starting to learn a new technology and wants to start with one working simple example - and I believe this is usually a very good approach when starting with a new technology.

In these cases, even basic research can be very time consuming, as the user doesn't yet know the relevant sources.

On the other hand, many times a solution for such an answer (or at least some guidance about how to approach the solution) is a no-brainer for an experienced user.

Additionally, these questions can be helpful to other new users of the same technology.

Considering these, there should be room for 'newbie' questions, as long that:

• Some minimal research was done, or at least there's a reason why it wasn't.
• The question should be clear
• The user should expect short answers, or be referred to more specific sources.

Answer 15

I'll keep this short and sweet, because I mainly want to talk about one major problem that hasn't been emphasized in the other answers: low effort questions require way too much mindreading.

The main reason I will vote to close low effort questions is that answering them is not about applying your knowledge of the language/library to the kind of problem they're describing, but an exercise in guessing the asker's intent. Having tried to answer these kinds of questions in the past, I know how often they result in the asker dismissing your solution entirely because it's not what they had in mind.

What they had in mind may have been something sensible, or something completely wrongheaded that results from their poor understanding of the tool they're using. Unless you can somehow intuit their exact situation from the details they've provided, you risk putting a lot of effort into an answer that will go completely ignored. Reputation points aren't everything, but they do provide a nice acknowledgement of your effort. Low effort questions break that feedback loop, drawing you into a back and forth with the asker that means the more effort you put in, the more they come back at you with new hurdles and obstacles.

Answer 16

Consider this flow. Someone posts a crap question. Someone else sees a kernel of internet usefulness in it, edits the question into shape, answers it. Who gets the rep, and subsequently the trust to push moderator buttons? The original, well, depositor. This is, from some sort of cosmic fairness standpoint, a reason to want to close rather than downvote.

What if, instead, we had no close votes? Any question that got a negative score and stayed there for a few days would, well, disappear. The justification is as follows: we want to remove the clutter of crap.

How would posters know what to fix without close reasons? Well, there are comments.

How would we get rid of spam? With flags.

In short, Shog's logic seems to lead in the direction of: if you think that this question is not going to lead to a better internet, downvote it. The site will take care of the rest.

As I read the traffic here, that leaves one bit of sociology. Help Vampires, we hates them. Many people 'round here, and I'm amongst them, get steamed by the spectacle of people trying to get something for nothing. Even if their question might become a popular internet resource (for other vampires?), we don't want to enable students to cheat their teachers and themselves, or people being paid to do a job to get away with gross ignorance. And we don't want them accruing rep.

The 'demand effort' department is, thus, part of the social contract. Some of us are willing to write answers if we can feel that we're not being suckered into doing other people's proper work.

The 'just downvote' system handles this. I'd downvote rather than answer.

What about the tendency of the unwashed masses to deliver scads of upvotes to crap questions? The 'close vote' system's 'giant downvote' is a way for people who have rep to outvote people who don't have rep.

Well, gang, if you like that, why not admit it, and make it explicit. Give people bigger downvotes as they earn more rep. And, as before, eliminate close votes.

Answer 17

For me it is really simple. I like answering questions if I think OP can (and wants to) learn something from it. If someone just wants code or debug a huge block of code (and therefore wants to abuse me as a free code monkey), it's not worth my time and energy trying to make an answer. It doesn't matter if OP knows anything about the subject, but from the nature of the question you can tell if

1. Someone wants to learn something from it
2. Someone will be able to understand your answer

Showing attempted solutions can or cannot be useful in a question. If the question is very simple, and the answer is very simple it is probably not needed to "show effort". If the question is confusing, because OP doesn't understand what the problem is, it requires a lot of effort to produce a correct (and useful) answer. Showing effort in that case means "I did everything I could to make the problem as simple as possible for you". The answer to a question should not take significant more effort than asking the question itself.

Should a question showing 'effort' be rewarded somehow? I don't think it should reputation-wise or something like that. Questions that show less effort than it takes to answer them should however be closed. What is 'effort' (or enough 'effort') should be judged on a case-by-case basis.

Answer 18

I've been conscious for some time of the fact that demanding that the question asker show their working can sometimes prove counter-productive. The trouble is that if the question asker has set off down completely the wrong path, then their description of their efforts so far is just noise.

For example, consider this edit of mine:

https://stackoverflow.com/posts/7092613/revisions

Leaving aside the stylistic and grammar fixes, most of what I did in that edit was removing everything the question asker had written about what they'd tried so far. And that made it a better question, at least from the 'body of knowledge' perspective, since it's now more succinct and easier to read, and doesn't distract the reader with an attempted solution that was totally misguided. I make many edits like this, that essentially just strip bullshit out of questions to reduce them to the shortest form possible that provides all necessary information, because that's what I expect to be most useful to future visitors.

Unfortunately, I fear that if it had originally been asked in its current form, it would have been downvoted and hit with "What have you tried?" comments.

Answer 19

Should Stack Overflow be awarding “A”s for Effort?

No.

Effort doesn't make a question a good question or a bad question. Someone who doesn't know how to debug their code won't be able to ask a good question. They may put forth a lot of effort in writing the question and providing details, however, if they can't debug, chances are their problem is simply a logic issue or a typo, resulting in a question/answer that is useful to only 1 person that will then never be used again, making it not useful. These kinds of questions used to get closed as too localized.

Examples:

Jquery prepend html syntax error " and '
Very common inner quote issue.

hidden element isn't shown by jquery
Duplicate id.

Add a speed paramater to the jquery plugin "Shorten"
Modifications to a plugin that isn't being maintained by it's author.

How to get all divs of a certain class and add innerHTML
Using a non existent method, doesn't know why it doesn't work.

The first two are just very common questions that come up and get answered several times a day. the third is someone asking for us to make modifications to a plugin for them (This question is actually a good question, it just would have been nice if he would have at least tried.) I don't even know what to say about the fourth question, he can't even see that there are errors happening on his page.

I don't think effort really applies in most cases. Either the person debugs the issue and creates a great question, or they don't and it's a poor question.

Someone who knows how to debug properly will generally include some of that debugging in the question itself, and if they don't, they will when we ask for it. I think lack of debugging skills is 90% of the problem. Answering a poor question anyway simply bypasses the problem, resulting in more poor questions. I rather try solving this problem than contribute to it by answering these poor questions.

Answer 20

The wording could perhaps use some improvement. Because it is so vague, everyone has their own interpretation of it.

For me, I view it as what I was told it would be for when the reasons were first brought up. When someone is directly requesting work in its entirety be done for them. To me it is the goto "help vampire" close reason.

Is this correct? I am not sure, but I am fairly certain no one really feels like turning in other people's homework assignments or re-inventing the wheel for them.

By the way, how would I write something like facebook but with more content in php? A+ please, I look at facebook all the time.

Answer 21

Visible effort is entirely beside the point.

If it's a good question -- one that might get googled, or others are likely to benefit from reading / learning -- then who cares how much effort the poster put in?

The question has to be clear and answerable -- and toward that end, some folks are better at asking questions than others; I've seen a lot of helpful comments try to nudge the poster to ask the question in a better way.

As for respect (for the answerer's effort) -- again -- beside the point. Not even Rodney Dangerfield could figure that one out. If it's a good question...great. If it's not, you can help to improve it, close it, or ignore it. Mundane, anticlimax -- as Kermit and Fozzy would say -- 'Movin' right along...'

Answer 22

What is wrong with answering a (simple) question instead of commenting: "try google", downvote the topicstarter and get 10 upvotes for that comment. Who's not showing any effort in this case? :)

Usually 9 out of 10 googles about code lead you straight back to stackoverflow.

Answer 23

Surely the important goal here is the production of well-asked, well-answered questions.

Agreed.

So a follow-on question:

Are we producing well-asked & answered questions which are accessible to the public?

When I ask google to help me find the answer to a programming problem, google often directs me towards Stackoverflow. The quality of the first SO answer that google directs me to is often “good” (subjective opinion of mine). Sometimes google’s first SO answer is inadequate, but usually one of the next few SO answers is “good”. I suspect that google directs towards “good” SO answers because those answers are visited more often.

Anyway, my point is that google does a good job of filtering the “bad” questions out of SO requests.

In my experience, Yes… we produce well-asked & answered questions which are accessible to the public.

In spite of a great quantity of “unworthy” questions, SO “distributes” well-asked questions with answers.

Now more to your question.

Some SO questions show ineffective effort:

• Homework where the well-asked question is really asked by the teacher without effort by the student,

• Code copied from a blog post plus the question of “How can I do [whatever] with this blog code”

• “Here’s my great idea in detail without code, please do all the coding entirely for me”

On my more-patient days I comment the questioner requesting a better question. On my more-impatient days I vote to close the question.

There is one class of ineffective effort question that I take the time to answer:

“I’m new here and I have only a few reputation points and I want to learn how [whatever] works”.

Sometimes the questioner may not be far enough up the learning curve to even ask an effective question.

In this case, I don’t mind taking time to bring the learner up to speed with a well-answered response.

I personally believe that a second important goal is to give help to those who “intend” to put in effort but who can’t muster up a well-asked question. (“Help will always be granted here at Hogwarts for those who ask—and are willing to put in present or future effort”)

It seems to me that answering these type of "willing to learn" questions eventually helps SO by giving the inexperienced questioner a chance become an experienced answerer.

Answer 24

I agree that effort in any form should be recognized. At the same time though, many users will ask a question on Stack Overflow simply because they don't know anything about the topic and actually aren't able to put in "effort" because of their lack of knowledge.

The demand for effort in a question portrays Stack Overflow as not being a good first resource, because it implies that the OP MUST have some former idea of the concept and have displayed that. I think that that shouldn't be the case, but at the same time, there has to be some standard on questions asked. There does seem to be a good standard in place and relatively easy-to-follow guidelines for question asking, but isn't clear exactly what the minimal "effort" required for a question seems to be. CUrrently, that seems to be determined by the community when they read a question and immediately post "Please see how to ask a question Here" or "Please do some research into the topic first."

My understanding of Stack Overflow is that it both is and isn't a place where answers can be doing the effort for the users, depending on the situation. The threshold for whether a question displays enough effort seems to arbitrary sometimes and other times obvious. Anyway, that's just what I think.

In terms of the title of this post, how would the "A"s translate into something tangible? Most people would assume reputation points, but what if a separate system could be implemented, that would update concurrently to regular reputation points? That could allow the user to achieve recognition for their "effort," but not go overboard to achieve reputation points. It could even be a track of badges that might eventually reward the OP with reputation points after 5 or so.

What do you think?

Answer 25

I think part of the trouble is that the system rewards answers to bad questions. If a Help Vampire (like the term, haven't heard it before!) posts a question with no code for example.

Not wanting to shoot-down a new user, you might comment to prompt him — 'What in particular do you not understand?', 'Can you show us the code for X and we'd be better able to help you', etc.

In the time you're adding your comment, or maybe cleaning up the formatting of the question itself, another user, Fred, has posted the complete solution to the question. Let's say this gets upvoted & accepted by the questionner — that's 25 rep points to Fred.

Fred has recently just joined & wants to increase his rep quickly to unlock more features of the site. This question was brilliant! He knew the answer off the top of his head & gained (at least) 25 points in 2 minutes.

& now we want Fred to start down-voting these questions — instead leaving comments or editing them? Why would he do that, when he can find similar questions & watch his rep rocket up?

---

I know we say that reputation isn't a measure of how good you are, it's how trusted you are by the community. The trouble here is that

1. New users don't necessarily take that on-board.
2. Fred should be less trusted by the community rather than more at this stage — he's adding to the problem.

Solution (?)

Why don't we use the question's score as a multiplier to the rep gained from an answer? E.g.

• A question is ranked <0, answerer gets 0 rep
• A question is ranked 0–10, answerer gets normal rep
• A question is ranked 11–100, answerer gets 1.5x rep
• A question is ranked >100, answerer gets 2x rep

The particular numbers above aren't important & would have to be weighed correctly, but it would actively discourage what at the moment is far too prevalent — answering bad questions for the hope that the questioner will upvote, even if it's useless to everyone else.

If answering a bad question was pointless, people wouldn't jump in to do it. & the reason we've so many bad questions, is that the questioner knows this too — they could put in effort and form a proper question, but if they don't bother, they'll still probably get the answer they're looking for before the question gets closed.

Answer 26

As per Stack Overflow,

Stack Overflow is a question and answer site for professional and enthusiast programmers.

Having said that, any question on Stack Overflow (part of Stack Exchange), I believe, is expected to be related to programming.

Regarding the question on homework or in fact work-related questions, there may be a few reasons why a question is asked.

1. Logic/pseudocode {not programming code related} [primary solution to the task]
2. Error or exception during run
3. Configuration issues
4. Lack of documentation/sample for APIs
5. Better or elegant solution (use of libraries, API, and tools)
6. Inconsistent/Unexpected behavior
7. Performance, etc.

Before we ask a question, it would be great if we have the answer to 1. For all other below, it may not be irrelevant to ask questions, even if it might seem of less research. As someone mentioned, we shouldn't be reinventing the wheel.

I have seen posts where people ask/comment: "Don't you use Google?"

Yes! People do. And they still may ask a question because they believe that answers on Stack Overflow are more credible rather than some random blog posts or incomplete documentation.

Also recently, on Google, if we search for any programming-related questions, Stack Overflow is one of the first links with relevant information. So it would be great if we build a database of good questions. Good necessarily doesn't mean not simple or not straightforward. It may mean something which is unique and can (or in future may be) searched for.

The only thing, we may need to follow is to ask a question as cohesive as possible; like just sticking to the point of issue/question. Also, presentation (including good formatting) matters to get good attention.