Mike Bernat has a new post that anyone, experienced or not in the development world, should read. The post is a good overview of how good developers (ones who really want a genuine answer and aren't just being lazy) should ask questions.

First of all, let me say this. If you consider yourself a developer and don't find yourself wanting to ask questions on a daily basis, you're doing something wrong. Asking questions without being afraid of humiliating yourself is critical.

His suggestions include not being afraid to over-describe the problem, speculate on what the possible answer might be (it can help to get the thoughts flowing), providing some examples of the problem you're facing and, most importantly, don't get offended by the responses you get. Sure, some might be blatantly insulting but those aren't worth the read anyway. Find value in the answers that can help, though - no matter how simplistic the advice seems.