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.
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
I feel like its worth adding, for those who don't trade. If the stocks goes down, you are looking for short/long terms supports it may [temporarily] stop on. Those are usually backed up by either history of the stock (recent supports) or psychological barriers (like a round number). In situation of a stock with couple hours of history those will be psychological like number 38. Then a trader looks how much support there is on certain level. In this example there were about $300MM (IIRC) worth of stock somebody asked to buy. So if you ready to sell because there is a panic and stock does not want to go up, you see so much cheddar [of support at $38] that someone is willing to buy that you tell yourself: "there is no chance someone will sell so much stock, so it won't go lower". So you don't sell at this point of time. Less people want to sell, more demand for the stock. Stock then stops or goes up, BUT at least the fall was indefinitely defended.
But again, depends what decisions big fish will do over this weekend, Monday morning you may see shit on $38, or if they offer plenty for sell at any price, you may see a gap down like start trading at $36.
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.
I suggest a "We don't offer our services outside of the USA for now. Leave us your email and country and we will notify you when…" somewhere in the ZIP code pop-in.
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.
That's exactly the point.One of the most promising uses of data that might be transmitted with this protocol is Behavior Based Maintenance. Most equipment maintenance these days is time based; the new goal is to be able to analyze data coming from the equipment (vibration, fluid flow, temperatures, etc) and predict that a failure is imminent and send a service person out before the equipment even shows any outward signs of failing.
Most of the businesses that want to do this don't even have the data they need to get started and don't have a clue where to begin. Having an industry standard comms protocol may be just what it needs to really take off. I've been watching the space for a while, looking for an opening that a startup can fit into.
Don't get too excited just yet - actually putting a sensor on everything would cost a huge amount of money and anything besides a passive RFID tag or barcode would need a battery. Consumers would need to pay an extra few dollars for everything and would need to replace batteries on everything they own every year or so. These protocols don't really do anything - the research community has bounced stuff like this around for a while. Someone actually needs to build better hardware before the Internet of Things vision actually comes true.
Yes, and frankly the micro-managing boredom. From my perspective, any system like this is starting to serve the needs of the platform in place of the needs of the consumer.
My car already has a light for when the oil needs to be changed. I don't need an oil-changer showing up at my door or the service-station calling me.
We have to fight for every ounce of privacy these days - why should anyone be expected to turn the whole life of their family into, essentially, an EZ-Pass?? No thanks . . .
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.
