3 ms·
It may well be underpaid compared to it's difficulty level, but the jobs exist. Meanwhile I've yet to see a Rails job that pays enough to be worth my while, de
by vidarh 4y ago
It may well be underpaid compared to it's difficulty level, but the jobs exist.
Meanwhile I've yet to see a Rails job that pays enough to be worth my while, despite Ruby being by far my favourite language.
I get to use Ruby a lot (rarely Rails; don't like the thing), but because I am typically in senior enough positions to have autonomy in what I choose for my projects - the moment a job is advertised as a Rails job, the pay is accordingly low.
- n0tth3dro1ds 4y agoThat's surprising for me to hear (as a non-Ruby/Rails guy that doesn't know that sub-market), given how many massively successful startups were built on Rails. I get that Rails isn't the hot new thing anymore, but Airbnb pays quite well and still uses it, right? Are there just tons of smaller fish paying peanuts?
- vidarh 4y agoIt's worth adding to this I've been developing software professionally for 27 years, so there being few Rails jobs meeting my expectations does not mean there aren't well paid Rails jobs. But Rails does best in a chunk of what used to be the PHP market for quick and dirty websites. Once companies scale, only a relatively small portion of their dev work tends to be Rails related, and not the most interesting/best paid parts of their dev work. The roles you can use Ruby in are wider and there is some juicier stuff there, but most of that isn't advertised as Ruby. E.g. in a lot of devops roles you may come across quite a bit of Ruby tooling.