[LRUG] Objects and on Hexagonal Rails

[Roland Swingler]

I think there are 2 factors that influence this:

* How large do you expect this project to get? The benefits of the
Objects-on-rails approach seem to be more applicable the bigger/more
complex the project; more debatable if you're going to end up with 20-30
models and you're mainly doing crud stuff. It's possible that you may have
a really complex section of your project where these ideas would shine, but
the rest of the project wouldn't see huge benefit over the standard rails
way.

* What sort of developers will you be hiring? Junior & mid-level developers
have a lot of resources in terms of books, community, other code examples,
etc. to learn how to follow rails conventions really well. Going for the
Objects on rails approach forces you into making many more, harder,
decisions - what is the scope for these decisions to be made poorly?
Appealing to authority, I seem to remember in the Domain Driven Design
book, Eric Evans advising that you shouldn't try and apply DDD if the
modelling skill in your team isn't high.

This might sound like I'm against the approach, which I'm not, I just think
it is more narrowly applicable than first assumed (not all projects need
it) and carries more risk (and potentially reward).

HTH,
Roland


On Tue, Jul 23, 2013 at 3:36 PM, Damon Allen Davison <damon at allolex.net>wrote:

> I think this sort of project is really exciting. How often do you get a
> chance to start with a completely blank slate?
>
> On Tue, Jul 23, 2013 at 2:26 PM, Tom Cartwright <tecartwright at gmail.com>wrote:
>
>> One reason (and I can definitely see their point here) is that intentions
>> can get obfuscated when using lots of loosely coupled objects and this can
>> lead to confusion. Given lots of developers will be working on the app,
>> onboard time is something I need to consider.
>>
>
> I suppose you *could* get confused, but I think that concern, while
> understandable, might be premature because your team's knowledge of the
> application grows as they build it. In my experience a nice outside-in
> approach to building your app would really help keep your team from getting
> lost in the possibilities.
>
> --
> Damon Davison
> http://allolex.net
> @allolex
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130723/d6147002/attachment-0003.html>