Just a brief thought while I was lazily flicking through the FAQs just now, avoiding work. It might well have been mentioned before, but perhaps worth adding as a further reason to IsolateTheProblem: I find, probably 50% of the time, when I'm preparing to ask a question here, and trying to create a concise piece of code that demonstrates the problem, that I spot the incorrect assumption / typo / general idiocy that was causing the problem all along, and don't need to post after all.
It saves time (both mine and other Ranchers'), I'm more likely to remember next time, and it stops me looking (quite so) stupid to the world.
This is a version of the "Rubber Duck Effect." If you have to explain something carefully, step by step to someone else -- even a forum audience or an inanimate object like a rubber duck -- if it's a silly mistake, you'll often figure out your own problem during the explanation.
Note that the FAQ is a Wiki -- you can edit that page all by yourself, and are in fact invited to do so.