Want to learn Rails? Start here.
zackshapiro.com
Want to learn Rails? Start here.
1–10 of 25 posts
Re: Want to learn Rails? Start here.
#2Usual things in rails is really simple but doing unusual things requires going down a rabbit hole of google searching, rdoc, blogs, etc due to the modularity (I had this issue with thor) of rails.
Re: Want to learn Rails? Start here.
#3Usual things in rails is really simple but doing unusual things requires going down a rabbit hole of google searching, rdoc, blogs, etc due to the modularity (I had this issue with thor) of rails.
This exactly describes my experience with Rails. It was so easy to do very normal things, and finding and extending gems was so much easier than doing the same with apps for Django, because in Django I basically had to rewrite every app I wanted to use (plugabiltiy was really bad, at least back in 2009-ish).
But with rails as soon as I wanted to do something less than extremely typical I was in a world of terror an ambiguity. It was so hard to figure out the "right" way to accomplish a lot of tasks.
Re: Want to learn Rails? Start here.
#4Usual things in rails is really simple but doing unusual things requires going down a rabbit hole of google searching, rdoc, blogs, etc due to the modularity (I had this issue with thor) of rails.
This exactly describes my experience with Rails. It was so easy to do very normal things, and finding and extending gems was so much easier than doing the same with apps for Django, because in Django I basically had to rewrite every app I wanted to use (plugabiltiy was really bad, at least back in 2009-ish). But with rails as soon as I wanted to do something less than extremely typical I was in a world of terror an a…
The ambiguity wrt choices is what gives rails it's large ecosystem (as well as semi high 'addon' churn). It's both bad and good, bad due to the huge amount of reading needed to fully understand a stack such as devise and good in that it allows such modularity.
Re: Want to learn Rails? Start here.
#5Usual things in rails is really simple but doing unusual things requires going down a rabbit hole of google searching, rdoc, blogs, etc due to the modularity (I had this issue with thor) of rails.
This exactly describes my experience with Rails. It was so easy to do very normal things, and finding and extending gems was so much easier than doing the same with apps for Django, because in Django I basically had to rewrite every app I wanted to use (plugabiltiy was really bad, at least back in 2009-ish). But with rails as soon as I wanted to do something less than extremely typical I was in a world of terror an a…
I think there are a lot of established "right" ways to do normal or fairly normal things, I think though with anything it's about figuring out what's right in the context of what you're building when you're off the beaten path. That's at least been my experience.
Re: Want to learn Rails? Start here.
#6So basically
1: Study it
2: When you're lost, research and ask someone
?
Re: Want to learn Rails? Start here.
#7So basically 1: Study it 2: When you're lost, research and ask someone ?
I think the real take-away is to give yourself an actionable/completable project, that you can devote significant blocks of time to, and then feel good when you complete them.
Re: Want to learn Rails? Start here.
#8Re: Want to learn Rails? Start here.
#9Earlier quoted context omitted.
This exactly describes my experience with Rails. It was so easy to do very normal things, and finding and extending gems was so much easier than doing the same with apps for Django, because in Django I basically had to rewrite every app I wanted to use (plugabiltiy was really bad, at least back in 2009-ish). But with rails as soon as I wanted to do something less than extremely typical I was in a world of terror an a…
The ambiguity wrt choices is what gives rails it's large ecosystem (as well as semi high 'addon' churn). It's both bad and good, bad due to the huge amount of reading needed to fully understand a stack such as devise and good in that it allows such modularity.
This is a lot of the reason that I don't recommend that students use something like Devise right off the bat. Putting things in middlewares is pretty great for separation of concerns, but it's confusing as hell if you need to figure out how something is done, and it's nowhere to be found in your source.