http://bikeshed.fm/5 "Rails is not your architecture"
podcast-bike-shed-episode-5-rails-is-not-your-arch#meaningless1 Like Avdi in podcast-giant-robots-39-avdi-grimm the guys think that the name is meaningless.
Service objects... the name is meaningless. One of the guys thinks that it should just be "objects". The other guy still puts them in the "services" directory, despite agreeing. podcast-bike-shed-episode-5-rails-is-not-your-arch#meaningless1
There's an idea of Query Objects (objects for really complicated scopes)
They talk about the same thing that happened to me... they didn't think to put non-activerecord models in "models"
Form objects... where does validation occur? He said, basically, that it should happen at the database layer, if the data is really important, and also at the form object layer (interestingly, not at the model layer... or at least that if it's not used in multiple places that maybe it doesn't make sense at the model layer).