It has become an issue that some questions have already been answered or people are being too lazy to look for the answers themselves.  There is also the issue of people not knowing what to ask or how to ask it as well as what information to give to make answering their question easier and faster.  We are not mind readers, we are not looking at your screen, we only know what you give us.

Prior to Asking

Don't be a Help Vampire and destroy the community. To avoid be such do the following.

1. look for the answer using the forums both here and WowStead's (Search Feature)
2. look for the answer using a web search
3. look for the answer using the FAQ
4. look for the answer by experimenting

Setting Up Your Questions

1. Post your question in the proper area
The forums are labeled. There is a questions section as well as a tutorial section. Your questions will go in the question sections unless it is specific to a tutorial then it should be posted on the tutorial posting.

Putting your post in the wrong area can lead to your post being overlooked or ignored.
2. Make sure your topic name is detailed about the post
Posting something like "Help Me!" could lead to your post being overlooked or ignored. It also makes it harder to help you if there are 50 "Help Me!!!" titles on the forums. As well as it is harder for future users to find the information that is on your post, which could answer their question or avoid them from submitting another posts very similar to yours.

Wrong: HELP ME!!!11!!!
Correct: YouTube video not displaying in forums
3. Make sure your post is grammatically correct
More often then not people who don't take the time to think out their posts usually don't think about their coding. This results in people not wanting to waste their time on those people. If you can't take the time to make your question grammatically correct then why should others take their time to answer?

Use punctuation and capitalization properly.This makes your post easier to understand and read. It's seen as a waste of time if first you have to "decode" the post before having to figure out what the question is.

Avoid:
1. L33t Sp34k - this is really annoying
2. ALL CAPS - this is seen as yelling and not a good way to get someone's attention
3. all lower case - fairly difficult to read.
4. Wrong use of words - Their, There, and They're, its and it's, etc.
5. txt chat - writing usually used in game or when texting such as u instead of you.
You have enough time to think, write out, and reread your postings. Firefox also comes with a spell check as well as a spell checker in the forums. If English is not your first language some mistake are understandable. A few misspellings is also understandable. It is understandable that not everyone is an English major, but there is a clear difference between being lazy with your writing and a few mistakes.
4. Make sure you're descriptive in your question
Post information that is needed in order to answer your question. This includes a link to where the issue is. If it is a custom content make sure it is set to public. Do not removed or altered the code you are having issues with. Include what you are trying to do is needed as well as what you have tried and the results. Some other information that is also fairly good to have is your OS, browser, resolution you are using. You can find this information here [LINK]. If you have coding from and external guide a link to that is also helpful.
5. Remember quantity does not equal quality in your post
When posting your question you don't need to add a lot of "fluff". It causes for more information that will need to be weeded through to decided what is needed. This is a waste of time and energy and can lead to your question being ignored. You can make your post descriptive without having a lot of useless babble. This includes portions of coding. Almost all of the time it's worthless to bother posting code. Just link to the area you have it and it will be seen there. Now if you understand coding and know where in the code it is you can post that section and explain what you see and understand about it.
6. Include what you have tried
Include what you have attempted to try to get it to work or fix it. This may include portions of code you are using (not the full thing). This will help figure out your level of skill to better assist you, if it is user error, if there is an actually bug that needs to be moved up the chain, that you are attempting to figure it out, and what you may or may not be understanding so it can be explained in a differnt manner to you to help you better understand.
7. Don't fawn... do research
Don't tell us you are a n00b or don't know anything about coding. If you want to be able to do something take the time to learn some of the basics. Tutorials are being marked with difficulty rankings. These are not suggestions. If you think you have enough skill to ask the question then you have enough skill to do a bit of research. There are several links posted to guides to help people new to coding. If you have a question post it, explain the issue you are having, but don't waste time, both ours and yours, by telling us you're a n00b. If you don't have the time to do some research we don't have the time to teach you the basics.
8. Describe clearly what you want to accomplish
Fairly simple. Explain what you want as a finish product, not parts of it. This helps your post clearly define what you want and what people can tell you to help you. As you could easily get two different answers if it's not clear, and there may also be a better and easier way to meet your goal if your goal is known.

Wrong: How do I put a music player on my site?
Correct: I want to put a flash MP3 player in the left nav as a widget without a header, but when I do I only get coding. What am I doing something wrong?
9. Don't ask other's to do your work
You get back what you put in. If you don't take the time to do research on your end why should other's do this for you? How are you going to learn if someone always does it for you? Asking for help on achieving your goal is okay, but don't ask others to do all the work for you.
10. The questions you ask will reflect the answers you get
If you ask a yes/no question you will get a yes/no answer. Don't ask if others can help or if there is a solution. There is no reason for this if you took the time to think about and write out a fairly comprehensive post.

Understanding the Answer

1. RTFM, STFW, and GIYF
Simple enough. Read the Fuckin Manual, Search the Fuckin Web, Google is Your Friend... Almost everything that is in tutorials or I have done I have found somewhere on the web. Almost everything I know has been self thought through using guides on the web. If you get a response like this then the information is easy enough to find and easy enough for you to understand and should be something you should already know if you are asking the question.
2. Don't understand
RTFM or STFW. Do more research on your end to better understand what you are needing to do. If you still don't understand reply by explaining what you know, what you understand and what are not understanding or what is unclear.
3. Rudeness
Often times people mistaken short, clean cut answers and replies as being rude. There is no reason for many answer to have warm, fuzzy, pink fluffy answers. This can lead to extra information that can then cause confusion. This is even more so when you are dealing with a large group of different cultures where some things could be easily mistaken for something it's not. The lack of a lot of "fluff" will also help you and others to find the answer you need within the answer given without having to weed through a ton of lollipops and gumdrops.

Straight forward answers is actually norms within most computer, coding, graphics communities because they are more concerned with finding the solution over making others feel special.