As some of you know, I maintain a food blog in which I try to have a lot of food porn … um … photos. Mix that with restaurant reviews/reports. The upshot is that I take the pics at restaurants with my iPhone. My iPhone 3GS. You know … the one with the (now) sucky camera. It sucks in low light conditions, producing grainy pics. It doesn’t have a flash. So dinners tend not to be too photogenic.

Enter the iPhone 4 with it’s low light sensor and flash (not to mention a 5MP sensor compared to the 3GS’ 3MP). I put off buying an iPhone4 for a long time (in Apple-years). I finally decided to go for it, in the name of journalistic integrity. And a desire to simply take more pictures. Sure, I have a better camera (5MB, glass optics, optical zoom, flash, etc) but it doesn’t fit in my pocket, not to mention it being unable to play Plants vs. Zombies.

So tonight before dinner, I stopped at the nearby (oh so deviously nearby) Apple Store and (with impressive efficiency from the staff) got an iPhone4. Since I a) wanted it for taking pictures, specifically in low lighting restaurants, and b) I had my iPhone 3GS in my pocket … I did a small exercise. At dinner (Cumin in Wicker Park … to be appear on CafeSnobisme) I took pictures of our dishes as I am wont to, with each phone. Here, side by side are the results. These are raw from the phones, uncropped and untweaked in anyway other than sizing.

All I can say is “Holy shit … that’s pretty good!”

Last post was Jan 18! I’m ashamed of myself. Then again my life totally changed (for the better) on Jan 19 and I’ve been busy catching up. I might write about that sometime .. but not now, and not here.

Update. I’m no longer with Engine Yard. I’m in the process of moving to Chicago and pursuing several opportunities there, and consulting at Groupon (with my good friends at Obtiva) in the interim.

And hopefully, I’ll be writing more here again. I have lots of ideas in the queue.

For my Google peeps. My buddy @stesla is giving a Google tech talk tomorrow at 11:30 in Paramiribo (techtalk 42) on BDD in Go including an introduction to the BDD framework her wrote: gospecify . We’ll be there for lunch afterward as well.

Nancy hit the ground running, whereas I ground to a halt. Ruby worked fine. Rails worked fine. Mysql worked fine. Rails wouldn’t talk to Mysql, though. After much head scratching, cursing, and frantic searching for liquor… I hit upon the crux of the problem. While I was installing the mysql gem… it wasn’t getting used. /usr/local/lib/ruby/1.8/mysql.rb was! To quote @thebloggess “The Fuck, Victor?!”

So a quick

sudo mv /usr/local/lib/ruby/1.8/mysql.rb /usr/local/lib/ruby/1.8/fucking-bogus-mysql.rb

later (with the mysql gem installed) I was up & running. A bunch of Ruby, Erb, CSS, and Javascript later and it’s looking pretty good.

All my blogging energies have gone into the EngineYard blog for the last while.

This is a just a note to say that Nancy & I are once again taking part in the rails rumble. This time focussing on getting shit done. Pure & simple. No detailed design or up front thinking.. just a general idea. No testing, think it up & code it up. And now we’re past the half way point and things are taking shape nicely.

We’re having fun and it’s something that might be fun to hack at afterward.

Well, WWDC is over. I made it this year… and glad of it. What a week (well, 4 days for me)!

Lost of new toys & tech. Lots of cool ideas for my after hours fiddling.

iPhone 3Gs, iPhone OS 3.0, Snow Leopard, new Mac Book Pros. It’s a good time to be a cocoahead. Go watch the keynote if you haven’t.

I’m pleased, tickled, elated, excited, and just plain happy to announce that I’ve decided to join the kick-ass folks at Engine Yard. Their focus is on-demand deployment and management of Ruby on Rails applications on Amazon EC2. They’re movers & shakers in the Ruby & Rails worlds (Engine Yard are the folks behind Merb & Rubinius, and are heavily involved in Rails).

I’ve had a mostly fun year & a half or so at Google. I met some cool people, who I will miss, and had some great food, which I will also miss (JC, both of those apply to you).

The reason for the change is that Google wasn’t taking my career where I wanted it to go. I took Chad Fowler’s words to heart (which were something I’ve tried to follow but sometimes get distracted from) “What would you rather be doing?“

I decided that what I’d rather be doing was: writing code, in Ruby, with awesome people, while contributing to the Ruby community, writing, and speaking. Being able to do all that in San Francisco… bonus.

So, here begins a new chapter in my career.

Thanks for all the well wishings & congrats from folks.

I was working on a post on the idea of us being professional, and that that even means. Mike Hill (@geepawhill) beat me to it. Go read his post. While you’re there, check out his other posts… it’s all good.

In his RailsConf keynote Bob Martin channeled Ward Cunningham to say that Smalltalk died because “It was too easy to make a mess”.

Whether Smalltalk is dead is the subject of much debate. Technically it’s not. There is ongoing development on the language and tools (notable by Cincom). But for all intents and purposes, it is no longer a commercially viable language. That said, it’s cool, and was a great context in which to learn OO. For that I am forever grateful to it.

I, personally, don’t think that “being easy to make a mess” was the cause of Smalltalk’s downfall. Sure, it was easy… but it’s easy to make a mess in any language. I have to agree with James Robertson that Smalltalk makes it easier to clean up your messes.

I was a serious Smalltalk user ‘back in the day’.. in the late 80s & early 90s: ObjectWorks, VisualWorks, Digitalk. I used it both in industry (some early CDROM shrinkwrapped products as well as client server) and academically (for my MSc thesis work). It was a wonderful language and environment. I saw firsthand, a few things that I believe lead to it’s demise:

• The unfamiliarity of the language and environment,
• The incompetence of the company tasked with commercializing it (ParcPlace), with their ridiculous licensing/royalty demands, and
• Arrogance, but not so much of the community, but of the environments themselves. It was beautifully cross platform, but at the expense of a truly native environment. In fact it was quite late into the game that you had windows out on your desktop instead of in it’s own self-contained world or even with simulated platform look & feel. As I said, that changed, but I believe it was too little, too late. There were some native implementations that were reasonably good.. but none approached the power of those descending directly from the PARC codebase. And Squeak, the shiny new smalltalk, goes back to that we-are-the-world arrogance.

So.. no… I don’t think what “killed” Smalltalk will kill Ruby. We’ve learned a lot since the 80s… a lot about how to keep a system healthy. The TATFT attitude is part of it. Notice I said attitude, and not practice.

We still can learn a lot from Smalltalk, specifically from it’s toolset. When we finally have good, useful Ruby IDEs they won’t look like Java IDEs. They’ll look like Smalltalk IDEs.

So… Smalltalk dead? Yes, no, does it matter? Smalltalk lives on in Ruby.

As I’ve mentioned on Twitter & Facebook, I’m back to doing Ruby & Rails fulltime.

Joining Google took me out of the Rails community & largely out of the Ruby community. At least until very recently when I joined a Rails project (yes, at Google.. who’da thought).

As noted on my blog last spring, I had the rug pulled out from under me with a sudden onset of diabetes.

With all that I pretty much pulled an Austin Powers and went into cold storage for a year & a half.

Well, I’ve thawed out and am back at it… Ruby, Rails, and hanging with peeps at conferences. Look for me on speaker lists before too much longer.

After GoGaRuCo and RailsConf, I’m back, motivated, and enthused like never before.