|Brian Donahue on 18 Sep 2007 21:11:45 -0000|
Expanding on the TDD topic, if I may boldly suggest work for others :) The biggest obstacle for me in really digging into Rails is that I come from a Java (long ago) and C# (now) background and have been influenced by the "Double-Ds:" Domain Driven Design, Behavior Driven Design, and Test Driven Design/Development. I have a pretty good understanding of how to apply these approaches in my familiar strongly typed, compiled languages, but when I sit down with Rails I get mired in the ActiveRecord and Controller implementations and feel like I start to write very procedural, unpretty code. I would like to see a real-world "enterprisey" (by that I just mean that it has more complex logic than a blog or some such) examples that show how the various layers, especially domain models/logic, are abstracted (or not) and why.
Perhaps that can be boiled down to this: I don't usually want my business objects coupled tightly to my DB tables a la Active Record, and I'm not sure if that is a good habit, that I can continue in Rails, or if it's just that I haven't grokked a different/better approach using Rails.
On 9/18/07, Mat Schaffer <firstname.lastname@example.org> wrote:
Wow... Are we gonna need a vote to narrow it down to two next month?
_______________________________________________ To unsubscribe or change your settings, visit: http://lists.phillyonrails.org/mailman/listinfo/talk