Like with everything tech I want to learn, I start by reading any quickstart guide is listed on the official documentation, then dive right into the guts of the subject. For Rails, this means running rails new on some empty directory and try to make some kind of app I already know how to build with other languages, for example the evergreen blog platform.
Normally, official docs + lots of googling and StackOverflow for every obstacle I encounter does the job nicely (at least for me)
Log in to continue
We're a place where coders share, stay up-to-date and grow their careers.
Like with everything tech I want to learn, I start by reading any quickstart guide is listed on the official documentation, then dive right into the guts of the subject. For Rails, this means running
rails new
on some empty directory and try to make some kind of app I already know how to build with other languages, for example the evergreen blog platform.Normally, official docs + lots of googling and StackOverflow for every obstacle I encounter does the job nicely (at least for me)