Stack Overflow Search – Now 61% Less Crappy
Remember when We Made Search 51% Less Crappy?
Well, we rolled up our sleeves and increased search quality a whole ten percent to 61%. How?
- Search now heavily weights title in the results, since people seemed to really like that approach. This is currently used on the /ask page, which does a title-exclusive search when you tab away (onblur) the title field.
Any individual search terms which map directly to the top 40 tags will be auto-converted to tag searches. So if you enter
it will convert to
automagically on your behalf.
This alone is a rather substantial improvement. One specific query, cited as an example of how bad the old search was, is to search for “what is a Monad”:
As you can see, pretty solid results now.
(And don’t forget to avail yourself of the Votes sort tab on the search results page. It defaults to relevance but sometimes votes is a better default sort IMO. There were users who almost literally fought me to the death on the choice of this default search results sort order in the Stack Overflow beta, so that’s how it is.)
I’ve also started implementing some BETA advanced search operators, as requested on meta.
The current advanced search operators are:
|posts from a specific user||user:1234 apples oranges|
|questions with a minimum number of votes||votes:15 apples oranges|
|questions that have an accepted answer||hasaccepted:1 apples oranges|
|questions that have no answers||answers:0 apples oranges|
|questions that have been closed||closed:1 apples oranges|
|questions that are community wiki||wiki:1 apples oranges|
Yes, these are a little buggy at the moment, but they mostly work. And they can be combined with [tags] and search terms of course.
One thing to bear in mind: the advanced search operators will sometimes kick you into a combined questions and answers search result format. So don’t be alarmed, when you decide to browse all posts by Jon Skeet voted up 20 or more times, that you see a mixture of questions and answers in your search results!
All of the above is documented on our new search help page:
Feel free to file bugs/feedback on this on meta, and please tag them with [advanced-search] if you’re talking about a search qualifier with a colon in it.