As programmers we talk about code smells, little cues that indicate we should be worried about a section of code. What are some Question Smells? Are there flags in questions that make you less inclined to answer them?
A question that's shorter than its title is a bad smell. It's not 100% accurate, but it does indicate that the question probably needs to be edited for clarity.
Question that have this pattern
/^I (want|have) to do(?!.*but.*).*$/ are often question where to OP is just looking for code and doesn't have actually tried.
Questions that contains
((please )?help me|thank you( in advance)?) are often bad question, because people who add that kind of formality often to do to compensate for the bad quality of their question.
what would be the output
Can't they just run the program and see the output. Yuuuu.
Signs that the OP already did some homework - like a list of things that they have tried, or a list of other questions (with a bit more explanation than just "they didn't work") - are usually a good question smell: It's either a good (hard) question, or an easy one that is worth answering.
The phrase "doesn't work" stinks to high heaven. It pretty much always requires us to ask the user follow up questions, like "what errors do you get?" or "what are you expecting to happen?".
Copy + pasted complete code files are almost always a bad question smell. They show that the OP has no idea which part of the code the problem occurs in, and they don't know how to use debugging to find out.
A pasted stacktrace, but no information about what they were doing when the error occurred or what the program is actually being built to do.