@cored that is a good approach to things, but I would prefer a directory structure like `app/services/<use_case_name_space>/<service_object>`, and perhaps the use case namespace should indicate that it is a service, either with a top level namespace (`Services::Events::Creator`) or following the Rails convention of ending names with the classification of the class (`EventsServices::Creator`).

We get people in this project with various skill levels, I just want to reach the point where we expose code which is readable and not too cryptic in its purpose. I think you have been doing great work so far in bringing this refactoring pattern into the project, I would like to hear your thoughts on how we can make this approach more friendly to people coming from different backgrounds.