Ranter
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
Comments
-
wojtek322113793dOof, from what you described, this seems like minor issues that should not have been escalated so publicly.
-
typosaurus1217493dWe did 360's and everyone had to tell three positive things about you and three negatives. Three is a lot. Since everyone gets bashed it's normal or smth. Fine for me, I'm master basher so people were nice.
But it sound toxic indeed. Kick him of the throne. New goal. No mercy. Grrrr! -
TeachMeCode517593dHe sounds like a piece of shit, scrum is NOT the place to discuss performance. That’s what 1-1’s are for. I feel bad you had to go through this hell
-
bosslogic19893dMost good developers would not get a kick out of brow beating juniors. This is probably an insecure mid-level who got a title somehow.
Of course, your financial situation, and the politics of that office, will inform you of what your choices are. I do think you should try to transfer if possible.
I'm senior and tend towards the opposite: if I think someone is doing poorly, I sometimes even refrain from making a comment in the repo since that's public. I'd rather approach personally and try to help.
Hang in there. -
vlord10192dI started back in 2009, and honestly, this kind of behavior has unfortunately become quite common. It’s something that happened to me, and I, in turn, did it to others. I’m sorry for having been part of these negative cycles, but when fairness is lacking, people tend to rely on their own moral compass. Sadly, many CEOs are more influenced by bad advice than good, and blaming someone else can still make you look better in front of most bosses—it works about 90% of the time.
By the way, have you heard of the Peter Principle?
So, I had to listen very badly in a scrum about my poor code quality. Just because I haven't used the latest version of the library in my gradle build file, I haven't used DTO in the response of few endpoints in the controller class instead I used entity,... Etc was the mistake.
I admit that I have a long way to improve myself and there is a lot to learn, but there should be a proper way to escalate the situation rather than publicly pointing out mistakes rudely.
He is a senior with 10+ years of experience who badly told me in the scrum and not only that whenever there is a change needed in my PR he takes the screenshot and puts it in our dev team group and shows the mistakes and gives the suggestions instead of writing comments on the github PR.
Not only that, if I inform in the daily updates that I took 2 hours for this and that task, he says it should be done in 20 to 30 minutes.
Upper management has given him a lot of respect because he is knowledgeable and knows the stuff but it doesn't mean he is entitled to behave like this and demoralise other juniors.
The matter is cool now but this incident happened to me a few months back and those days were really toxic for me at work.
rant