There is a huge learning curve with Rails, insofar as it is its own "opinionated" framework with numerous conventions, if well-chosen, that are unique to Rails. You can deploy web apps in Rails without adopting all of these things, but you will never be respected by Rails developers (I've heard devs say "that's not the Rails way" countless times). Usually these conventions are chosen for good reasons (even though they frequently change), but impose a significant cost since you have to learn:
(1) Ruby the language
(2) Idiomatic Ruby as perceived by Rails Devs
(3) Rails conventions
(4) Appropriate plugins/addons
All of them take a decent amount of time to learn (well). 3 & 4 also change pretty frequently.
So, it is possible you "grok" everything quite well (I'd guess that you do), but haven't learned all the specifics that make things tick the "Rails way."
(1) Ruby the language
(2) Idiomatic Ruby as perceived by Rails Devs
(3) Rails conventions
(4) Appropriate plugins/addons
All of them take a decent amount of time to learn (well). 3 & 4 also change pretty frequently.
So, it is possible you "grok" everything quite well (I'd guess that you do), but haven't learned all the specifics that make things tick the "Rails way."