Wes Maldonado: Data Junkie

Eventual consistency. The storage system guarantees that if no new updates are made to the object eventually (after the inconsistency window closes) all accesses will return the last updated value.

My coworker wrote up our experience writing ruby integration tests against Amazon SimpleDB. You should know that we were in an integration test that runs infrequently. Production code should not use this retry method. You should be using exponential back off when you get an error code. I’ve heard that not doing this is the equivalent of crossing-the-streams in Ghost Busters.

Here are some must have bash PS1 commands if you’re working in multiple branches with various SCMs like git, svn or bzr. With this in your .bash_profile you’ll end up getting the following PS1

wesmaldonado:(git)gchartrb[master]/$

wesmaldonado:(svn)wumpus_project[trunk:141279]/$

Found at Lazy Bash cd aliases. The latest can be pulled from github:

http://github.com/relevance/etc/tree/master/bash/bash_vcs.sh

“You can’t compare this to South Lake Union or downtown,” he says. “Not all areas are created equal.” Jeff Thompson, of the Freehold Group, the development company that has spearheaded the Dravus effort Seattle Times: Red tape fences in Interbay overhaul

Have a look at this google map for a compare and contrast

View Larger Map

A story about an internet crush…

… a few weeks later when I checked my spam filter. “Congrats–most women have to meet me at least twice before a crush wears off,” he’d replied. Cute. I replied, and we ended up having a bizarre but hilarious (to us) discussion about HTTP error codes. (Reproduced after the jump for the curious.) Fellow Metblogger Josh once told me upon reading that conversation, “I can’t imagine how things between the two of you didn’t work out.” And sometimes I wonder the same thing.

Go read the ongoing story at Single in Seattle: Blogger Boy No. 2

Charles Nutter had the following to say on the maglev ruby performance numbers:

Except that these are results reported entirely in a vacuum. Whether this is fib following the “rules” of Ruby is entirely an open question. Whether this is method dispatch adhering to Ruby’s call logic is entirely an open question. Whether this is a while loop using all method calls for its condition and increment steps is an open quesetion. Because the Maglev guys haven’t started running Ruby tests yet. Is it Ruby? http://headius.blogspot.com/2008/06/maglev.html

I am interested in maglev ruby because I’ve met some amazing smalltalkers who worked on large systems using gemstone. Want to know more about the size of systems gemstone is designed for? Have a read through this PDF: GemStone and Orient Overseas Container Lines:A Shipping Industry Case Study I think having more implementations is a great thing and will help

What do you think? Will the we use it if it’s closed source? I bet some people will, if nothing else this primes the pump for the next generation of programmers that will maintain systems like those of OOCL.