I'm not a web-application developer, so writing Ruby on Rails code is basically just a past-time. In as much as I like Ruby, being a very elegant and expressive language to code in, I can't exactly say the same for Rails (at least not yet).
'Convention over Configuration' is a good idea, but problem is, sometimes you've got to know what conventions you to be looking out for to do something, and not knowing it can make it a rather frustrating experience, especially when you are starting out.
In order to map out all facets of an application access patterns into conventions, it is also inevitable that there will be much to read and make sense of. Probably something to take note of, and not to mistake that Rails will automatically translate to easy!