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
-
I've been there and it sucks.
Staying in a job where you do outdated things decreases the pride or self esteem as a developer, and it can also mean not learning as much you would in another job.
Of course though, stay if you need the money.
You could also be a culture setter and be the guy that people look up to to learn, to doing things the better way.
I think it's important being vocal and honest (with respect ofc) with the upper guys about your opinions on the current workflow and how you could improve it.
If no one in the company gives two shits about your intentions, then I'd say lost case, so you pretty much need people to care and be passionate about development.
Propose trying out slack to improve the communication, and organize it properly. -
@erandria so I had a conversation with my manager about the team. He said that whatever I don’t see I have to get it implemented and provide functional training for. Perfect I love it, I told him about the lack of teamcity, communication within the team, the lack of git and the reasoning I got was that since the project is only 1.5-2 years old there was no time setup a process. Also okay I guess I understand. Here’s the real kicker, he said since you have had experience with the firms deployment tech stack (mind you I only started this job in August) I should be the one to implement this, alongside my usual work from the ALM.... I just hope these devs will follow this.
Related Rants
It changed my life, really. 😁
Clients be like...
So I graduated last year learned everything I would need to succeed in the job world. I got to my first rotation, I solved a total of 6-7 jiras in the past 6 months. I got to my second rotation, my new team is pretty much all remote and it’s been 2 weeks that i have been sitting idle. Their code base is not on git they’re not organized as my first one and I’m confused as to what they do, there’s not really any confluence and the deployment of code is done via uploading a jar. I really want them to adopt a structure like my last team or something similar because but I don’t know enough how to implement a new deployment process. I feel like sitting idle is the worst so I’m gonna start to see if I can implement a proper structure for them but who knows if they’ll even use it.
rant
work
newteam
newbie
javadev