We all know what a googlewhack is, and that they're increasingly hard to find.
But what happens when you turn to Google for an answer to a problem that you're working on (say... trying to get VMware's Web Management Interface to work in IIS7), and the third entry in the list of results is a link to your own site/blog?
Only, you know you don't have the answers - otherwise you wouldn't be looking on Google. Sadly, at that point, I think you're hosed. And you know it. Hence, googlehosed. Maybe the 'rule' for being googlehosed should be that you know you're google-hosed when you see one of your own entries/posts on the first page of results - especially if it's BEFORE you start scrolling?
Sadly, however, this happens to me more often than I would like. I just never expected it for something as simple as getting the VMware web admin portal working in IIS7...
I'm always happy to find a result with me in the top hits... even if it doesn't solve my problem.
Oh, and here's a googlewhack I just thought of: "otorhinologist grass"
Posted by: jon Sharp | November 06, 2007 at 01:24 PM