Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
I'd recommend spending a lot of time with Ruby itself before adding Rails to the picture. Ruby is a super-powerful language, almost like C++ when it comes to the number of language features you have available to solve any particular problem (which can be a good thing and a bad thing).
I tried learning Rails before without a concrete understanding of Ruby, and I succeeded in making a site, but my code wasn't elegant and nothing I learned soaked in because I was constantly having to go look things up and didn't understand Ruby enough for them to click in my head. I've been learning Ruby the past few months without even touching Rails and I've I still feel like I've only scratched the surface!
Building 🏗 https://turnshift.app, Shift Scheduling for Slack Teams.
Also:
https://nextjsnews.com
https://github.com/vvo
https://dev.to/vvo
Before: JavaScript and support
@algolia
.
Thanks Scott! I guess experience differs for me here, using TryRuby and the Learn Enough Rails tutorial was sufficient for me to get enough Ruby to feel comfortable. I come from the JavaScript world also and actually the different language features and concept are similar, even if syntax differs.
I would maybe avoid spending months learning Ruby if your goal is to build a product, because it seems a very long time. But it depends on your needs.
Still, super important to learn Ruby first and then continue learning it yes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd recommend spending a lot of time with Ruby itself before adding Rails to the picture. Ruby is a super-powerful language, almost like C++ when it comes to the number of language features you have available to solve any particular problem (which can be a good thing and a bad thing).
I tried learning Rails before without a concrete understanding of Ruby, and I succeeded in making a site, but my code wasn't elegant and nothing I learned soaked in because I was constantly having to go look things up and didn't understand Ruby enough for them to click in my head. I've been learning Ruby the past few months without even touching Rails and I've I still feel like I've only scratched the surface!
Yeah, always learn ruby first. You'll enjoy rails more when you know how to write ruby.
Thanks Scott! I guess experience differs for me here, using TryRuby and the Learn Enough Rails tutorial was sufficient for me to get enough Ruby to feel comfortable. I come from the JavaScript world also and actually the different language features and concept are similar, even if syntax differs.
I would maybe avoid spending months learning Ruby if your goal is to build a product, because it seems a very long time. But it depends on your needs.
Still, super important to learn Ruby first and then continue learning it yes.