Ways to Decompose Fat ActiveRecord Models

Re:Ways to Decompose Fat ActiveRecord Models by damoncali on Wednesday October 17, 2012 @11:03AM (#4664729)

Perhaps it's my lack of training or the projects I work on, but I've never seen a Rails model so large/cumbersome as to justify even one of these techniques.

Is this a case of fixing the wrong problem?

[ Parent | on HN ]

Re:Ways to Decompose Fat ActiveRecord Models by jweir on Wednesday October 17, 2012 @11:25AM (#4664839)

I have a project which will benefit from Bryan's advice.

There are models which are overly large (the project started as a Rails 1.2 project now at 3.0). The project has moved through different hands and the cruft and bloat has built up.

I look forward to applying some of Bryan's points to these models.

[ Parent | on HN ]

Re:Ways to Decompose Fat ActiveRecord Models by brynary on Wednesday October 17, 2012 @11:05AM (#4664741)

Not all apps require these techniques to stay maintainable. My background is working on larger Rails apps, built up over multiple years by teams of 6+ people, so the post is shaped by those experiences.

[ Parent | on HN ]