So the Google Buzz API has been available for a month and I've added all kinds of value to this example code. Below is a link to all those folks I follow (who have supplied an image):

It's trivial and yields a social graph in four lines of code essentially. Nice! The only thing we needed to consider was the use of response.data.entry instead of response.data.item which became obvious by looking at this JSON showing who I follow on Buzz.

Because most of our data-related time is in XML land immediately we think XSD and find there exists something similar for JSON. JSON Schema! The Address Schema, for example, looks reasonable but we wonder how necessary all those double quotes might be. They seem to be redundant tokens that only reduce readability. Otherwise it's friendly enough.

Migrating from a database we quite like to one we do not provides as much fun as surgery.

After the DBA has promoted the database into QA we find our application is spouting Primary Key violations because the sequence.nextval values are below those used within their respective tables. Identity columns. Yet another reason to prefer SQL Server. There's a clear pattern here.

Sure, there are some advantages but we'd take portability over the possibility of having more than one auto-generated sequence any day.

It's interesting catching the impressions of an Oracle expert going the other way. Oracle to SQL Server: Crossing the Great Divide, Part 2. The comments in Part 1 make for a fun read. Especially those that bemoan the developer tools. Toad's okay.