Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
TrevorTheRat10645dAt least you got offered a yoga session, that’s more than most places. Most places will just tell you that it’s your responsibility to educate them
I am in my twenties and I work every day with 40+ devs. From my experience, they don't easily adapt to new changes and usually come back to the way they used to do stuff.
You gotta reach a certain threshold with them, speaking about time, before they start to understand they must adapt. It's pretty weird to say but basically you gotta think they are like kids who gets zero or little value from changing the way they used to code in the last 10+ years.
Aside from the time it takes to change, you probably have to deal with the "who cares“ attitude which is pretty common in European people, at least where I live. Don't take it personally, don't even cry, you should put away your passion at work. In my opinion the best piece of advice I can give you is the following:
" The workplace is not the context where you express your passion "
Yep, sounds weird but you have coworkers and management with pov and priorities different from yours.
I don't think you should complain with the management, they probably know you have a tough job here. Just keep delivering anyway, in the end if someone complain you can always point out you did the best you could to improve situation, the team is cooperating but slowly adapting.
I'm saying this because management is not expecting to get your complains. You have got the job to introduce changes in this prehistoric environment. They don't want to deal with it so they hired you to deal with it.
I'm in a similar situation. Fellow devs are not too old but the application is over a decade old. Their practices are... Not ideal. I have seen code that's not even maintained in source control.
I joke around that half of my job is to complain enough that something changes.
What I have done is:
1. I introduce improvements in the process whenever possible and MAIL THEM TO THE TEAM with direct managers in cc. It sounds a bit naggy but it's to prove to management I am not just complaining but doing something about it.
2. Show them the benefit of said improvement. Maybe time savings, more stable build, whatever
3. Befriend fellow devs. People are more willing to help when you're nice to them.
4. Let go of your frustrations when they don't do as you say. In the end, you can't control people. You've done 1,2,3. You've done your job.
If you can't do #4, find another job.
resignation is the only way i guess need to find a new job first though, good luck with your struggle.