Lately, no matter where you look, the unthinkable is being thought of.
Google Mail has been down for last 40 minutes. Sitting here at downtown Reston's Panera, I have connectivity to any other site to which whim takes me. Just not Google Mail.
Sites like this don't have scheduled outages. At least this used to be the case.
Generally, I recommend Google. This most recent email outage is starting to put dents in my trust. After their Feb 09 outage, you'd think they would've pulled out all the stops to make sure mail service wouldn't die only a few days later.
We cannot spend our way to good economic health, even in the short run. We have to produce.
John Stiglitz, Chief Economist of the World Bank from 1997 - 2002 took callers on CSPAN this morning, one of which was a democrat who suggested (paraphrasing), "With the economic downturn and the tax payers being the problem, with the bad mortgages and such, why not just give every American one million dollars? Then people would spend money, helping businesses, and letting people keep their houses and jobs."
Why stop at one million?? Why not 10? How about 100 million? We'd all be set for life.
I'm all for consumption as a important part of market health. However, the problem with consumption based on money given versus money earned is that, when given, you have no skin in the game. No risk taken. This changes everything. If you lose it all because of a bad decision, oh well.
With money earned, you have a vested interest in not seeing it disappear. With money earned, you do your best to get the maximum value you can for every penny. This kind of incentive works. Money-given based consumption eventually reduces productivity to point of total dependency. This is socialism and, as history shows, has a strong track record for destroying markets.
Considering Groovy for your next big project? We did. All things considered, it figured to be a safe choice given its Java pedigree. From the limited exposure I'd had to Groovy up until that point, it looked and felt remarkably familiar to Ruby (a good thing). I had even heard you could cut & paste any amount of Java into a .groovy file and it would just work. Depending on what 'work' actually means, this is mostly true.
One of the small untruths about Groovy behaving 'just like Java' is worth serious consideration - especially if you want your .groovy code to become API-ready.
Jim Weirich, Joe O'Brien, and Chris Nelson acted out a dialog where they built an application to reserve conference rooms. Very entertaining and novel approach for a tech conference! I loved it. But, to the point now - the summary...
So, you want to build something?
Their are at least two philosophies to fleshing out the model: Traditional object-based modeling and behavior-based modeling. How are these different?
Portland, Oregon is, well, Portland (overcast and wet). Got in late last night and walked over to Stanford's. The service was friendly, even at 10:30 PM. Everything about the burger was above average. And it came with hot, crispy, slightly salty fries. It was all devoured with sips of a local wheat bear that I forget the name of.
So far, having been away from Ruby and Rails for over a year, it feels like going back to a place you used to live. Some things are still the same. In other ways, I hardly recognize the place. New techniques like elastic computing (and plenty of competing commercial hosting options), new tools such as git, tarantula, and hobo, etc. Good stuff.
I'll pretend I blog and let you know how it all goes.