Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Gotta be realistic on the workplace. And there’s marginally decreasing returns at play too.
Shit code, shit pay = grind for experience job jump ship asap
Great code, shit pay = charity work, stick it out a bit longer and get good skills
Great code, great pay = recognize it when you got it. Great code is not perfect.
Shit code, great pay = you’ve gotten golden handcuffed, you aren’t really growing but they’re paying you to give up and maintain their monster
What are your thoughts on jumping ships often to get higher salary?
I feel it doesn't make sense if you are really into learning. From what I've seen, when you become senior or have more responsibilities, the work that needs to be implemented takes more time. Because these responsibilities include aligning multiple teams in the company. Jumping ships won't let anyone experience the work.
I'm not against getting higher salary. But is jumping purely for that reason sustainable in the long run?
question
career switch