2. follows rails conventions on recent rails version
3. good work environment.
12 thoughts on “almost every rails job?”
The more experience as a freelancer I get the more I experience that #2 is harder to find than I would have guessed.
A lot of jobs that are looking for Rails devs aren’t really “Rails” projects, as much as they are illustrations of Ruby’s “sharp knives” in action. You still have to be a good chef.
A “Rails backend + React frontend” is usually a big red flag, but a lot of these jobs get advertised as needing a “Rails” developer. In reality they are marginally Rails with a pastiche of patterns copied from random ideas popularized in the world of JS / microservices trends.
I really identify with this. I started a job about a year ago working on a 12 year old rails app and it has been exhausting to work on. The pay is good but every time I see a 7+ year old commit by Kevin in the git blame, I know I’m about to have a really bad time. Damn you, Kevin.
3 is non-negotiable. The other two I can make tradeoffs. A bad codebase can be refactored gradually. A company with the best culture isn’t necessarily rich.
The only thing I can’t do is microservices.
I realize more over time that Rails is a drawer full of sharp knives that the average idiot only knows how to make a mess with, even though you need those knives to write simple code too. In my work I try to have high test coverage and stupid simple code now.
Yep, finding that out also. You’d think people who call themselves Rails developers since the early 2000s would understand why Rails conventions make the framework great to work in when you embrace them, but… no. The siren’s call of microservices is just too much for so many people in early development.
Wow. My last job I had 2 and 3 – startup with a bunch of very young people. Now it’s 1 and 3 – huge company with people from all backgrounds. I much rather prefer making exactly double, after tax. Though I try to enforce 2 as much as I can, but it’s just impossible.
The more experience as a freelancer I get the more I experience that #2 is harder to find than I would have guessed.
A lot of jobs that are looking for Rails devs aren’t really “Rails” projects, as much as they are illustrations of Ruby’s “sharp knives” in action. You still have to be a good chef.
A “Rails backend + React frontend” is usually a big red flag, but a lot of these jobs get advertised as needing a “Rails” developer. In reality they are marginally Rails with a pastiche of patterns copied from random ideas popularized in the world of JS / microservices trends.
I really identify with this. I started a job about a year ago working on a 12 year old rails app and it has been exhausting to work on. The pay is good but every time I see a 7+ year old commit by Kevin in the git blame, I know I’m about to have a really bad time. Damn you, Kevin.
Currently migrating a Rails app to v4.2. I know what it’s like to pray for death.
I’ll take 1. and 3. Thanks.
3 is non-negotiable. The other two I can make tradeoffs. A bad codebase can be refactored gradually. A company with the best culture isn’t necessarily rich.
The only thing I can’t do is microservices.
I realize more over time that Rails is a drawer full of sharp knives that the average idiot only knows how to make a mess with, even though you need those knives to write simple code too. In my work I try to have high test coverage and stupid simple code now.
. #1 and #3 all the way. Those two are important to me and not my job to fix. #2 is what I’m hired to work on… it’s opportunity.
It would be very hard for a company to get 2 and 3 without 1
I’m struggling to find a dev in Brisbane Australia that I think would say they get all three…
I’ve built a greenfield project with rails 7 – using turbo stream and Hotwire.
valley office with an awesome team and a very good salary!
Yep, finding that out also. You’d think people who call themselves Rails developers since the early 2000s would understand why Rails conventions make the framework great to work in when you embrace them, but… no. The siren’s call of microservices is just too much for so many people in early development.
I feel we’re doing a reasonably good job at all 3.
these 3 arent mutually exclusive. Almost every Rails company I know they have all of these.
Wow. My last job I had 2 and 3 – startup with a bunch of very young people. Now it’s 1 and 3 – huge company with people from all backgrounds. I much rather prefer making exactly double, after tax. Though I try to enforce 2 as much as I can, but it’s just impossible.