I routinely find the question I'm asking has already been answered when googling, and have rarely had a question go unanswered.
The hard part in my experience when going to try and answer some questions is it seems like there are more and more questions by inexperienced coders expecting people to write basic code for them, or not formulating the question in a way that will be useful to others in the future - instead they're pasting in their code and asking, "why isn't this working". Instead of, "I would expect this framework to behave as follows but it's not" it's "Here's 50 lines of code, why isn't it working?" The only way to answer such questions is to get their code up and running somewhere, perhaps on a jsfiddle, figure out what's wrong (often something as trivial as a syntax error), and then tell them. Doesn't feel very gratifying to do one off debugging on behalf of the person asking especially if the answer is unlikely to be useful to others in the future.
The hard part in my experience when going to try and answer some questions is it seems like there are more and more questions by inexperienced coders expecting people to write basic code for them, or not formulating the question in a way that will be useful to others in the future - instead they're pasting in their code and asking, "why isn't this working". Instead of, "I would expect this framework to behave as follows but it's not" it's "Here's 50 lines of code, why isn't it working?" The only way to answer such questions is to get their code up and running somewhere, perhaps on a jsfiddle, figure out what's wrong (often something as trivial as a syntax error), and then tell them. Doesn't feel very gratifying to do one off debugging on behalf of the person asking especially if the answer is unlikely to be useful to others in the future.