Helping devs understand concerns faster

[santib (Santiago Bartesaghi)]

@ferngus

These are software design techniques, not Rails or even Ruby specific. Prescribing which techniques to use is a divisive topic. How to implement a given technique is also subject to individual preference and style.

I completely agree. My point is that Rails is creating for us the concerns folder but it’s not the services or other folders suggesting structure/design patterns/whatever.

I don’t like to be insistent but I’ll try to make clear my point one last time (I promise ). I think the output of this topic should be either:

1. Rails stays accountable for the concerns folders created by default when running rails new and adds documentation on why are they creating them, thus avoiding confusion

OR

2. Rails removes the creation of concerns folders by default when running rails new, thus avoiding confusion