bryanthompson

The main benefit that I see in writing for the filesystem first is that you _can_ defer the decision of database type and structure until it actually becomes important, then you can make that decision for each component of the system and swap them out independently.

The typical process, for me at least, has been to write out all the requirements of an app, then to start building migrations, models, and tests. Flipping this around has made me think about each layer differently and it _does_ blow minds when you show a simple "jack" that can be swapped out for any type of database at any time without affecting anything else.

Exactly what stopped me. I'd upload my Gemfile.locks, but I had to bail out at the github login screen.

I never would have guessed it before they released their Simple Workflow Service. Once I saw that, though, game on.

After I saw @unclebobmartin speak at Ruby Midwest last year, I got so flipping excited. I walked away with goals of having tests that ran instantly, layers that were as independent as possible, and wanted to build this master framework he described so cryptically.

I think programminggeek nailed it here. If you watch Bob's talk, then watch the Obvious screencast, you'll see that this is a serious attempt at this dream architecture.

http://www.confreaks.com/videos/759-rubymidwest2011-keynote-...