Rails definitely has its downsides but your experience in the job market is strange to me.
Ruby on Rails developers these days are in short supply. During the pandemic I secured two jobs (first one sucked) in Ruby on Rails developer positions. Back in 2017 I took a coding bootcamp for Django/Python but when I saw how little those jobs paid I stayed with Rails.
There are a lot of hectic changes but thank God for those. If it were the same as it was 15 years ago there wouldn’t be a chance anyone would use it. The hype crowd got scared off in the early days but modern Ruby is pure bliss to work with.
I feel your pain. Before landing where I am now I was tasked with bringing a Rails 3.22 (edit: it actually took me about a month before I knew the true version because it was a forked 3.22 with a ton of 4 back ported into the fork) app up to Rails 7.
There seems to be a lot of bad design decisions in the earlier versions of Rails — for the most part I’m referring to the users of Rails (developers) rather than developers of Rails itself.
Ruby’s downfall is that unless you’re an experienced developer it’s pretty easy to get by with poor design decisions. I’m literally explaining myself: I’m self-taught but I didn’t start coding professionally until about 4-5 years ago. I run a small business on the side that’s powered by my very own old code without tests, huge models, and cringeworthy blocks of code.
What I think you’ll find is that it’s mostly senior positions open. A lot of companies wrote something quick back when Rails was the hot new tech, let it go for a decade and then started screaming “help!” at the job market when things started breaking.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
Rails definitely has its downsides but your experience in the job market is strange to me.
Ruby on Rails developers these days are in short supply. During the pandemic I secured two jobs (first one sucked) in Ruby on Rails developer positions. Back in 2017 I took a coding bootcamp for Django/Python but when I saw how little those jobs paid I stayed with Rails.
There are a lot of hectic changes but thank God for those. If it were the same as it was 15 years ago there wouldn’t be a chance anyone would use it. The hype crowd got scared off in the early days but modern Ruby is pure bliss to work with.
deleted by creator
I feel your pain. Before landing where I am now I was tasked with bringing a Rails 3.22 (edit: it actually took me about a month before I knew the true version because it was a forked 3.22 with a ton of 4 back ported into the fork) app up to Rails 7.
There seems to be a lot of bad design decisions in the earlier versions of Rails — for the most part I’m referring to the users of Rails (developers) rather than developers of Rails itself.
Ruby’s downfall is that unless you’re an experienced developer it’s pretty easy to get by with poor design decisions. I’m literally explaining myself: I’m self-taught but I didn’t start coding professionally until about 4-5 years ago. I run a small business on the side that’s powered by my very own old code without tests, huge models, and cringeworthy blocks of code.
What I think you’ll find is that it’s mostly senior positions open. A lot of companies wrote something quick back when Rails was the hot new tech, let it go for a decade and then started screaming “help!” at the job market when things started breaking.