"reclusive but highly intelligent stereotype", lol now I don't feel so bad. but seriously, I can't get this bing social search to work. I've tried keywords I've seen occur many times in my facebook stream. It doesn't appear to be doing any "social searching".
funny, I was bummed python came before java on app engine. and what about gwt? that's java! who would want to write their javascript in javascript anyway ;-)
and yes, I agree that the mindset of learning new things in your free time (and bonus for open sourcing work) is the way for a software engineer to stay gainfully employed. worked for me.
nice idea. I tried to setup a new a/b test for a site and it became 'not easy' when I wanted to track an adsense click as a goal.
I wrote a manual a/b test for the same site about 7 years ago, and got adsense click goals working with 40 variations of the page, after about a week of working on it after work at night after my regular job.
There is some jquery code you can add to track javascript events which would probably track adsense clicks, but it's 'not easy', ie: I might as well not pay for it.
Cool idea though! I would pay for it if I could track adsense clicks without having to write code. Also, having an option to select multiple dom elements at once would be nice. In addition, logging into the web site and editing the html to add the code in the <head> tag would be nice too, especially since it's kind of a hassle for me to open eclipse and re-deploy to app engine at 1am when I am tired.
I believe there's a few reasons. one is that the google file system blocks that bigtable runs on and "reads" for your query could be on any number of machines. been a while since I read the google architecture papers but I would recommend it to all. it is fascinating how they implemented gfs, bigtable, chubby lock, etc. the work around is essentially to write your own code that does what a database does - something to the effect of getting a list of keys for the records you are interested in and using that to then scan just the area in your data structure you want.
I love the document record pattern. I use this on google app engine, which is a tad tricky to use as a relational db. It actually ends up being way simpler and faster. For instance, you can model an app with just one "table" (Kind). You can put say a user id primary key, then have blob binary data fields which store your serialized document records. The reason it's so fast is all you're doing is a simple index scan to lookup all the data you want. It also makes it really simple to store items into memcached/memcache.
Seriously, $175k a year and you get an article in entrepreneur magazine and 26 points on hn? Really? They must not live in the bay area!