My comment on his site:
"This is the nature of the beast. Developers build software. The good ones support it, and the bad ones make it someone else's problem. The good ones write documentation, and the bad ones tell you to read the code.
I can sympathize with your situation. I go through something similar nearly every day at work, but I am not the kind of person who will tell someone to %!@# off because they don't know how to search for errors in Google.
Searching for errors with google is strange at first for everyone I think. The best thing to do is to both answer the question directly and refer them to a google search that would give them the same answer (with the keywords you used, and perhaps WHY you chose those keywords). I know it sucks, but I remember being a greenhorn and not knowing how to search for some syntax-laden error, which parts of that error would help me in Google, and so on. Some of it was brute force, and some of it was learning by example.
In short, don't be so quick to assume someone is lazy for asking a question. Don't be so quick to assume someone is stupid because they haven't been Googling compiler errors for 10 years. Google has a simple design, but that doesn't mean the construction of queries is equal in its ease. I think most people need a refresher on Boolean logic and how it works in their queries. Google has pretty much put that in their black box, IMHO, to the detriment of a lot of newbs to the net. Perhaps google should consider putting up a little mini guide on how one might search for things they find in particular contexts. Errors should certainly be in that list. I consider myself a pretty good Googler (although I think this mentality is the same as everyone believing they're good at driving or thinking they themselves have a good sense of humor), but I would happily read an official Google writeup on tips for extracting good search terms from example contexts.
"