This morning (Sunday) there were 100 new questions per hour appearing on Stack Overflow. The key to getting your question picked out of the masses and answered is a well-phrased title, a well-phrased question body with sufficient info to understand the issues, and a good choice of tags (though don't overdo the tags). A "niche" question is not a problem if you can attract the right interested person -- many people on SO relish such questions.
On May 21, 4:39 pm, Julius Spencer <[email protected]> wrote: > Wow, thank you everyone for the answers! I suspect the questions may be too > niche which is why I'm not having much luck. > > Cheers, > Julius. > > On 21/05/2011, at 10:51 PM, Mark Murphy wrote: > > > On Fri, May 20, 2011 at 10:27 PM, Julius Spencer <[email protected]> wrote: > >> After attending IO and talking to the engineers, I was told to put > >> questions on stack overflow. I was wondering - how do I get people to > >> look at these? > > > Based on the last set of stats I ran, 83% of questions posted on > > StackOverflow in the android tag get at least one answer. 47% have an > > accepted answer, meaning that the person who posted the question > > agreed that an answer solved their problem. Not all people who ask > > questions accept answers, so the percentage of questions getting > > correct answers is probably somewhere in the 50-60% range, if I had to > > guess. > > > As DanH indicates, question quality is one key determinant of success. > > The more information (e.g., stack traces, snippet of source showing > > where the crash occurred) you supply, the easier it will be for > > somebody to provide an answer. If your question pertains to subsystems > > beyond pure Android (e.g., SQLite, WebKit), tag the question for both > > android and the other piece of tech, to expose the question to more > > experts. > > > Another thing that causes questions to go unanswered is if they're a > > bit too niche. The question may be perfectly valid, even exemplary, > > but if there aren't that many people who might know the answer, you'll > > have poor odds of one of them happening to try to answer your > > question. Similarly, StackOverflow, like this list, is best for SDK > > questions -- firmware questions tend not to fare as well. > > > -- > > Mark Murphy (a Commons Guy) > >http://commonsware.com|http://github.com/commonsguy > >http://commonsware.com/blog|http://twitter.com/commonsguy > > > Android App Developer Books:http://commonsware.com/books > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
