Real World Ruby Application Creation and Work Flow

Hey team,

I've got a real world case study which I've been planning out for some time now, and ready to start building a v0.1 prototype.

When I say planning, I mean I have a good idea about my database and how I want tables to join relationships etc.

I've got a blank ruby canvas in front of me!

In some of the Ruby application building videos here on Treehouse, Models, Controllers and Views are created alongside functionality. For instance in the Odot video series, the todo_list model, controller and views are created first, followed by todo_items followed by users etc. I would describe the build process as pretty modular because each model is fully functioning before another is added. Maybe this is a side effect of generating scaffolds?

I'm drawing my comparison against the ActiveRecord series. Don't get me wrong, I understand the goal of this series is not to create an entire application (i.e. controllers, views, behaviour etc), but I quite like the idea of getting the models in ActiveRecord set up, using the console to moderate and check model behavior and validations.

I think I've already picked option two - i.e. get the relationships set up first, and then play with the results, but unsure if this a good way to go with Ruby, considering this is dissimilar from the various 'build an application' videos.

If you have any insight, it would be great to hear from you :)

Thanks :-)