<story><title>Rails – The Missing Parts</title><url>http://eng.joingrouper.com/blog/2014/03/03/rails-the-missing-parts-interactors</url></story><parent_chain><item><author>ollysb</author><text>Perhaps because it&amp;#x27;s written with examples in java but I often feel like no one in the rails community has ever read Eric Evan&amp;#x27;s Domain Driven Design[1]. It&amp;#x27;s far and away the best material I&amp;#x27;ve ever seen on how to organise large code bases. It covers pretty much every suggestion that I&amp;#x27;ve seen from the rails community. Sometimes the rails community can feel like the fitness industry, everybody just rebranding things that have been done before.&lt;p&gt;[1] &lt;a href=&quot;http://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.amazon.com&amp;#x2F;Domain-Driven-Design-Tackling-Complexi...&lt;/a&gt;</text></item></parent_chain><comment><author>kohanz</author><text>I would argue that both the Rails community and fitness industry may operate that way, but for good reasons. Any time you have an ongoing an significant influx of beginners, looking to hit the ground running, bad practices will be everywhere. A handful of established &amp;quot;bibles&amp;quot; or textbooks aren&amp;#x27;t going to be enough to get the message out to the masses. It may not be appealing to those already &amp;quot;in the know&amp;quot;, but good practice messages need to be repeated and communicated in new ways. You also see the same dynamic at the gym, of the experienced gym-rat lamenting the things that personal trainers get paid to teach newbies.&lt;p&gt;In that same vein, this may be a repeat message of a concept that is not novel, but as an experienced non-web developer who is fairly new to Rails, I learned something from reading this.&lt;p&gt;I also appreciate you pointing out what sounds like a good development resource (Domain Driven Design).</text></comment>
<story><title>Rails – The Missing Parts</title><url>http://eng.joingrouper.com/blog/2014/03/03/rails-the-missing-parts-interactors</url></story><parent_chain><item><author>ollysb</author><text>Perhaps because it&amp;#x27;s written with examples in java but I often feel like no one in the rails community has ever read Eric Evan&amp;#x27;s Domain Driven Design[1]. It&amp;#x27;s far and away the best material I&amp;#x27;ve ever seen on how to organise large code bases. It covers pretty much every suggestion that I&amp;#x27;ve seen from the rails community. Sometimes the rails community can feel like the fitness industry, everybody just rebranding things that have been done before.&lt;p&gt;[1] &lt;a href=&quot;http://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.amazon.com&amp;#x2F;Domain-Driven-Design-Tackling-Complexi...&lt;/a&gt;</text></item></parent_chain><comment><author>hiphopyo</author><text>Is &lt;a href=&quot;http://tech.taskrabbit.com/blog/2014/02/11/rails-4-engines/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;tech.taskrabbit.com&amp;#x2F;blog&amp;#x2F;2014&amp;#x2F;02&amp;#x2F;11&amp;#x2F;rails-4-engines&amp;#x2F;&lt;/a&gt; another one of those?</text></comment>