An Annoyingly Efficient Relevancy Engine
Tuesday, November 13th, 2007There are a lot of things in The Nerd Handbook that I can really relate to.
There are a lot of things in The Nerd Handbook that I can really relate to.
We just rolled out a new site search feature at DS, using Apache Solr as the search backend. We are making use of several of it’s more resource intensive features, including faceting (on a bunch of fields) and the dismax query parser.
It brings me an immense amount of pleasure to see that someone has de-obfuscated and reverse-engineered skype [PDF]. It describes how to detect and block skype traffic, in addition to how to find and screw with the network control elements. We can only hope that someone takes this a step further, and writes bridges between the skype network and real VOIP networks.
Rebecca sent me a link to an article describing POSH - Plain Old Semantic HTML, which does a pretty good job of explaining the basics of the clean HTML I wish I saw in more websites.
While looking into setting up a logging framework within our code, I came across an article that discusses logging the FireBug console from within PHP. Coupling this with the PEAR::Log documentation on redirecting non-fatal PHP errors, I now see PHP errors in my FireBug console, rather than in my pages.
The first article also mentions FirePHP, which consists of both a PEAR extension for PHP, and a FireBug extension for your browser. This combination allows for much more structured debugging information to roll up to the browser, but at this point it seems to still be somewhat beta.
While researching the optimum way to design large tables for InnoDB, I found an article entitled How to Exploit MySQL Index Optimizations that provides some good information about the differences between MyISAM and InnoDB index structures, and how to optimize your tables for each.
An older article from the same site provides a bit more information.
This is pretty amazing, if you are a vi user.
Here is a nice visual representation of the various different kinds of table joins you can do in SQL.
Here is a handy article about the anatomy of credit card numbers.