It is rare to get a frank appraisal from someone who has seen both worlds. Thank you!
Would you advise a programming newbie to skip Ruby and go straight into the JS world? Rails is easier to learn, and it's good to learn multiple stacks, but on the other hand there are not many junior positions for Rails. It's true that I could learn JS frameworks after Rails, but I'm not sure that is worthwhile. I don't have infinite time to learn everything and then get a job. Maybe Rails is easier for a solo learner to build portfolio apps with? But if there's no Rails job at the end of the tunnel...
The author’s critiques about Rails are mostly valid: it’s important to recognise its limited palette of abstractions and move beyond them when needed. Many Rails teams don’t have the modelling experience to make this transition well, and that’s why so many Rails apps end up as big balls of mud.
But as a way to iterate, prototype, and get from 0- something very fast, there’s still very little quite like Rails out there.
Thanks. That is reassuring. I did a quick job search, and I see that there are plenty of jobs out there. Even if I will have to look harder for a junior position, there is hope.
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.
It is rare to get a frank appraisal from someone who has seen both worlds. Thank you!
Would you advise a programming newbie to skip Ruby and go straight into the JS world? Rails is easier to learn, and it's good to learn multiple stacks, but on the other hand there are not many junior positions for Rails. It's true that I could learn JS frameworks after Rails, but I'm not sure that is worthwhile. I don't have infinite time to learn everything and then get a job. Maybe Rails is easier for a solo learner to build portfolio apps with? But if there's no Rails job at the end of the tunnel...
There are definitely Rails jobs to be found!
The author’s critiques about Rails are mostly valid: it’s important to recognise its limited palette of abstractions and move beyond them when needed. Many Rails teams don’t have the modelling experience to make this transition well, and that’s why so many Rails apps end up as big balls of mud.
But as a way to iterate, prototype, and get from 0- something very fast, there’s still very little quite like Rails out there.
Thanks. That is reassuring. I did a quick job search, and I see that there are plenty of jobs out there. Even if I will have to look harder for a junior position, there is hope.