Skip to main content

Page Chunking, Like Chunky Milk, Is Bad

Search results suck past the first page. Google might have a billion results for some search, but it won't give them all to you in the result page. You are probably only interested in the first five or so results. To be nice, you get a whole ten results on the page. If you want more, you need to go to page after page of ten results at a time, possibly millions of pages worth to get every single result. Obviously, you won't do that, and for two reasons:
  1. You don't care about all ten of the results on the first page, much less the thousands or millions of other result pages.
  2. Refining your search is far easier than going through one page at a time.
Having or bringing the information you want to the top of the listing is better than looking for it further down in the listing. That being the case, our solutions should center around making it easier to bring information up from the mountain of results, instead of finding ways to bury you inside of it.

Some interesting headway has been made with the universal search features launched by Google. You can shift your search focus to their different specialized searches. Ask.com has some of the most interesting result filtering, with their Narrow and Expand search suggestions. Rather than paging through results or manually trying to alter your criteria, they will split the results into logical segments, and point you to what your current results might be a segment of.

Another interesting filter tool could be result voting. I imagine a small - link on each result, which when clicked will remove the result, along with any very similar results in the entire set, and will reorder the remaining ones based on how similar they are to something you have deemed completely irrelevent. This would be a great way to filter similar termed, but logically different concepts. There are rumors that Google is testing such a feature, but I have not seen proof of this yet.

What other ways can we dig through the mountains we are mining?


Technorati Tags: , ,

Comments

Steve Spalding said…
As for the voting thing, Swicki has a very similar sorting method. I suggest giving it a look if you haven't already.

Popular posts from this blog

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…