3 ms·
I am pretty much saying that Google/Search should find what I intend to look for rather than its interpretation of what I type into the search field. Because t
by waterlesscloud 17y ago
I am pretty much saying that Google/Search should find what I intend to look for rather than its interpretation of what I type into the search field.
Because that's clearly how the general public intends to use Google/Search.
The only reason I don't use it that way is that I've learned to adapt to its shortcomings. I'm better than most at finding what I want using Google because I've learned to speak in Googlese, so to speak. How to frame my query in a way that returns what I want. I've adapted to the tool rather than the other way around.
Clearly that's a bit much to expect of the masses, who are very often frustrated by Google/Search. I'm not running down the masses here. They want to get things done. We have very basic tools to help them, I'm arguing that our tools should be orders of magnitude more sophisticated.
Sure it's hard, and while that response may be satisfying for engineers, that doesn't solve the problem people are trying to solve when they use Google/Search.
And honestly, there's just something plain wrong with your algorithm when it returns a news story as a top result for "facebook login". It's a safe bet that is NOT the result 99.999% of the users are looking for when they type that in. And if you're failing your users a very high percentage of the time, the problem simply does not lie with your users.
- philcrissman 17y agoI honestly don't think I actually disagree with what you're saying; I just still don't see this as a "failure" on Google's part, and that was the impetus for the post. I don't think Google should have been expected to anticipate this sort of thing. Learn from it? Sure. Expect it? I still don't think so.