brendino

It's related to the Dell - VMWare reverse merger. They have to raise cash to fund the merger.

A flash game I built in high school (about 7 years ago) went from an average of $30 per month on AdSense to $500 the next month, to $3,600 the month after that due to an unexpected surge in traffic for a keyword for which it ranked #1 on Google. The $3,600 month happened in May, and it has since dropped steadily to about $1,500 a month now. Regardless, it was a nice surprise since the game was just sitting there from when I spent a weekend building it a long time ago.

While the implementation of this would be pretty straightforward, the method signature you're asking for seems convoluted, in my opinion. Here's why:

- "add1" is not very descriptive of what the method actually does, since it adds one, but only sometimes. This title makes it sound like the method simply increments each value by one.

- When you say "if it is zero, do this, but if it is positive, do this...", this thinking creates a "secret handshake" in your code, so a new developer would have to read the method in depth to understand what it does in each case.

- If this method will have widespread use in your code for arrays, consider extending the array class with the method, so that you can call it directly on an instance of an array.

I propose you change the method signature to:

  increment_where_value_equals(value, options = {})

So you could call it like:

  increment_where_value_equals 1, { :direction => :forward, :limit => 2 }

or even like:

  increment_where_value_equals 1

While the implementation may get a little more complicated this way, you're making the method signature much more clear and descriptive, which will lead to better code overall.

The greenshoe increases the demand. MS placed a 38.00 bid with an enormous size, so if you were to look at the live feed, you would have seen something like: Bid: 38.00 x 9999999 Ask: 38.01 x 1234

Update: we ended up second place in the Ann Arbor Hacka2thon. GooseCast (ccgoose.com) took the top honors. Thanks for everyone's feedback so far!

For now we're pretty much only targeting the US (hence the zip code thing). We originally had browser geo-location, but disabled that for a few reasons. We will re-enable it soon.

Actually, that's already a feature! In the bottom left you can specify a date range.

FYI - Please click 'allow' when your browser prompts for geo-location. If you don't see many events around you, log in with Facebook and the system will fetch publicly-available events that are connected to your and your friends.

This has huge implications - imagine every "thing" having a freely-available API. Combine that with predictive analytics and we can come really close to predicting the future.

What an incredible idea! This can become even more valuable if ifttt can open its platform to enable outside developers to create and distribute custom action blocks and triggers for end users (like an app store of ifttt triggers and action blocks).

Furthermore, I can see this transitioning into "phsyical" applications (think "The Internet of Things"). For example, OnStar can connect car sensors to send a text message when your car leaves your garage.