@vitobotta This is a weird article. It feels like the title was written first and then the body tries too hard to convince us it’s actually the case.

I’m low-key looking for a job right now and my feeling doesn’t match the article.

For one, there used to be a lot of openings 5 years ago. Places like WeWorkRemotely used to overflow with rails/ruby jobs. Now it has 1. Job board on the rails site has 20.

Now, the article is incorrect that remote is standard. Many big companies stopped doing that. They have big offices and want them to work. E.g. GitHub used to offer a lot of remote. Now only a handful of openings. Same goes for other big Rails companies like Shopify, etc. At best they give you a hybrid option.

Then article goes to contradict itself by saying that remote is there because big cos don’t want to pay SanFran/London salaries. First, London is already like half of SanFran in a good day. Then you look at the rest of UK and it’s maybe £70k ($90k) which is not too bad but rare. If you got Spain/Portugal you’re firmly in $50k territory. You go to Eastern Europe and ugh. I saw opening in Baltics (which is EU) for like $35k/y. Big oof.

I haven’t seen a single opening for a greenfield rails project. Which means no Solid Queue because they already have chosen a background job infra a decade ago and it’s most likely Sidekiq. Same goes for most newer rails features. I saw Hotwire a few times but react dominates.

Another tendency is that classically rails shops are switching away from rails. Many still run rails in production but most new work is done in something else. Most often go and python. Python of all things! You go to UsingRails.com and a solid half of the companies have openings for anything but ruby/rails.

Rails is a great framework. I’d even wager the best web framework out there but it’s clearly on its way out. Which is a shame.