4
int32
8h

spent the whole week working on a bug fix last week.

implemented a method to filter some data to make it easier to use in the HTML template.

friday's session with other programmers to review code went well, they said the method is pretty good and works nice. (I must admit there was an elusive bug that prevented the component to render and none of us could figure it out)

i get back on monday to a message from the lead saying the code is unusable and they reverted to the previous (convoluted) way of doing things and i should do the same in the future. just copy their work.

i check the typescript class. fucking method that was used (which he told me not to use and I should copy and work off of), he went and just changed the method's name, and the body is EXACTLY the same as his existing method.

this code base is ridden with re-used methods (I managed to extract two reused ones into a service some time ago), the use of any for 90% of method return types and variables...

WTF. I am losing all of my respect for seniors and faith in this company.

This is why I am burned out. You are farting against a hurricane and everyone else's shit is coming back onto you. This is fucking insane. Or am I insane?

Comments
  • 2
    Sounds like your senior deserves a swift kick to the dick, though it sounds like he already took one to the ego. Current PM would do the same, such losers
  • 2
    @BordedDev yeah i have a really bad vibe from this dude. been having it for a long time now. i don't know why, though, maybe I intimidate him or something with my skillz. i'm not even that good of a programmer.

    i brought up code quality issues twice before in retro meetings without being a bitch about it, i thought long and hard about softening the blows and he ended up basically telling me to shut up about it in a private message.

    this is why i am burned out. reading their shitty convoluted, difficult to maintain and extend code.
  • 2
    @int32 Hmm funny PM did the exact same, in the end I gathered enough screenshots to report him. They didn't fire him unfortunately but he did stop being as much of a pain for a bit after that.

    He also does like to shit up the code, literally have a PR right now that will disable checks in his "merge release branch back in" PR meanwhile he will cry if we "contaminate" one. Unfortunately, there is no point in pointing out issues in his code because he will just stone wall and stick his head in the sand and if he has to wait he will eventually just skip requirements, so instead we have to get a new PR done, approved and then sneak in the fixes :/

    Not sure what advice to give to be honest other than hopefully find a new group to work with or check with the others if they have the same issues with the PM and you can make a group complaint
  • 3
    @BordedDev some people are just toxic assholes, tbh. I've worked at this company for almost 7 years and have never ever had these kinds of issues as when I joined this team earlier this year.

    I've made my decision to leave the company, already talking to recruiters and have job interviews lined up. I also rejected a few because of stupid code tests.
  • 2
    @int32 Nice I saw you mentioned that in the other rant, I've been wanting to do the same but have just had a lot going on atm outside of work + I am currently the only profitable person in the company, but my care for the people there is waning heavily over these last couple months :/

    (It's a contracting company and the PM is part of the client I work for)
  • 1
    @BordedDev omg that sounds gnarly. PMs can be such fools. It's like nobody cares for the software dev's mental health in this industry.
  • 1
    @int32 seniors just don't really review theur code. You need a review buddy that you have understanding with like they do. I had often problems with people working longer than I did at places too. The rules are just not the same for everyone and it takes some time before you can join the corruption .
Add Comment