Personally, I believe that the best teachers are those that teach their students how to learn - ultimately, the job of a teacher is to put him or herself out of business (with each individual student, of course). Once a person is able to teach themselves, the world is their oyster, so to speak...
As far as it concerns the OP's (or other's similar) thoughts:
If you want to receive good answers to your questions in the Arduino forums - be sure to provide us with your complete source code, your schematic and/or hookup diagram (we much prefer a schematic if you have one), as well as clear pictures relating to your project (ie - with a schematic and a clear picture of your breadboard, we can easily spot bad connections, for instance).
Don't give us links to another website showing someone else's implementation (pictures, schematics or code) - we need to see your implementation. I cannot tell you how many times questions have gone round and round with people seeking help, only to find out that they had made a wiring mistake, which we could have spotted fairly quickly had they originally provided us with pictures, etc of their project.
Post your complete code (and use the code tags!); if your code is too large to put in a single post, then provide a link to a github or similar shared area. Sometimes we can diagnose an issue with just a snippet of code, but more often than not, the complete code will reveal to us problems that can't be found with just a snippet. If you can't post the complete code, schematics, or other parts of your project (due to any number of issues), then you may find that we won't be of much help.
Learn how to properly ask questions:
http://www.catb.org/esr/faqs/smart-questions.html
Also - don't expect answers immediately - don't sit there waiting, "bumping" the thread every 15 minutes or so; more likely than not, that will just turn off people from helping you. Instead, use your waiting time to think about your problem, and other ways to potentially find the problems or fix it. In other words, be productive with your time waiting - you might just fix it before anyone else does! Be sure to update the thread if you try new things and get results that seem promising (or that fail as well). Most of the time you may have to wait a while, simply because people are trying to look at the problem, understand the issues, and figure out a solution. Some of them (depending on the problem of course) may be trying to replicate your project, to see if they can get the same failures to occur, and how to fix them.
When someone gives you advice, try it out. Don't just sit there and contradict them, or tell them "no that can't be it" - unless you have a really good reason why that would be (and provided you gave us a proper description and such about your project, and asked the questions properly - then you should have addressed those reasons anyhow from the beginning). Nothing is more frustrating than someone asking for help only for them to turn around being contrary after you have given them help.
Also - don't claim you are an engineer or some other high-falutin' title, and then go and ask questions that make us wonder what box of cracker jacks you got your degree from. We can see through that a mile away; we also don't like doing other people's homework for them, and we see those kinds of questions often as well at certain periodic moments (on this and other electronics forums we are on - we all have seen it, we know when the waves are about to start with people asking for homework help - we don't mind honest questions toward understanding, but we don't like being conned into doing someone's homework).
