Im a junior SWE who recently made a switch from L1 support within the same company. When I first joined the team, our most senior engineer was helpful, knowledgable and approachable but recently I’ve realised more and more how massive his ego is and how he looks down on people with less experience.
Here’s what happened today:
– In a private chat, he asked me how I even tested and merged my PR when it doesn’t even compile
– I told him that it did compile when i merged it
– He insisted that whatever code was in my PR should not be able to compile
– I showed him receipts of the builds in the pipeline which show that the PR compiled successfully
– He then doubled down and accused me of changing the code after the last successful build because it definitely doesn’t compile now
– Soon after, he realised that the reason the code was not compiling was another dev (A) had created a feature branch from dev at the same time that i created my feature branch
– In my PR, whatever code that dev A was working on did not exist in my branch
– I changed a function signature, compiled, tested, and merged my code
– A week later, dev A merged new code that using the old function, causing it to not compile
– Why dev A did not pull changes from dev after I merged or resolve merge conflicts is beyond me but that is not the point
– Senior engineer came at me demanding why I changed the function signature
– I saidI couldn’t remember why I did, I reviewed my own code and admitted that everything would have worked fine if i hadn’t
– He said that because of this change, i broke dev A’s code
– This pissed me off so much because dev A’s code didn’t even exist at the time of the merge, I had no way of knowing changing a function would break his code in HIS branch
– I defended myself aggressively saying that I shouldn’t be taking responsibility for code breaking
– Senior engineer then said its not about assigning responsibility or blame but about understanding what changing functions that are intended to be shared can cause as we don’t typically pull changes in from dev before merging (?? not sure what he’s talking about here because i definitely make it a point to fetch changes so i can resolve any conflicts early)
– I tried responding professionally by saying that i own the mistake of changing the function without a good reason but that i would appreciate if we can clear misunderstandings of what the mistake was before saying things like i didn’t compile or test my code
– He didn’t take this kindly focusing on the fact that I did in fact change code that resulted in someone else not being able to compile theirs and that he pointed it out so that i understand what can be the consequences of doing such things, at this point i left it as it was cos i was fuming
Anyone in my position receiving accusations like that would have felt like he was definitely trying to assign blame. This isn’t the first time this has happened, he has displayed an enormous sense of superiority to anyone with less experience, even heard him refer to devs in other teams as r*tards for not implementing certain things in a way he deems proper. To make things worse, he’s slated to become my manager before the end of the year and seeing as he doesn’t think highly of me, this could be a serious detriment to my career just as I’m getting started. Anyone has faced a similar situation? Any advice on how to deal with this is appreciated
submitted by /u/bobbledog10
[link] [comments]
r/cscareerquestions Im a junior SWE who recently made a switch from L1 support within the same company. When I first joined the team, our most senior engineer was helpful, knowledgable and approachable but recently I’ve realised more and more how massive his ego is and how he looks down on people with less experience. Here’s what happened today: – In a private chat, he asked me how I even tested and merged my PR when it doesn’t even compile – I told him that it did compile when i merged it – He insisted that whatever code was in my PR should not be able to compile – I showed him receipts of the builds in the pipeline which show that the PR compiled successfully – He then doubled down and accused me of changing the code after the last successful build because it definitely doesn’t compile now – Soon after, he realised that the reason the code was not compiling was another dev (A) had created a feature branch from dev at the same time that i created my feature branch – In my PR, whatever code that dev A was working on did not exist in my branch – I changed a function signature, compiled, tested, and merged my code – A week later, dev A merged new code that using the old function, causing it to not compile – Why dev A did not pull changes from dev after I merged or resolve merge conflicts is beyond me but that is not the point – Senior engineer came at me demanding why I changed the function signature – I saidI couldn’t remember why I did, I reviewed my own code and admitted that everything would have worked fine if i hadn’t – He said that because of this change, i broke dev A’s code – This pissed me off so much because dev A’s code didn’t even exist at the time of the merge, I had no way of knowing changing a function would break his code in HIS branch – I defended myself aggressively saying that I shouldn’t be taking responsibility for code breaking – Senior engineer then said its not about assigning responsibility or blame but about understanding what changing functions that are intended to be shared can cause as we don’t typically pull changes in from dev before merging (?? not sure what he’s talking about here because i definitely make it a point to fetch changes so i can resolve any conflicts early) – I tried responding professionally by saying that i own the mistake of changing the function without a good reason but that i would appreciate if we can clear misunderstandings of what the mistake was before saying things like i didn’t compile or test my code – He didn’t take this kindly focusing on the fact that I did in fact change code that resulted in someone else not being able to compile theirs and that he pointed it out so that i understand what can be the consequences of doing such things, at this point i left it as it was cos i was fuming Anyone in my position receiving accusations like that would have felt like he was definitely trying to assign blame. This isn’t the first time this has happened, he has displayed an enormous sense of superiority to anyone with less experience, even heard him refer to devs in other teams as r*tards for not implementing certain things in a way he deems proper. To make things worse, he’s slated to become my manager before the end of the year and seeing as he doesn’t think highly of me, this could be a serious detriment to my career just as I’m getting started. Anyone has faced a similar situation? Any advice on how to deal with this is appreciated submitted by /u/bobbledog10 [link] [comments]
Im a junior SWE who recently made a switch from L1 support within the same company. When I first joined the team, our most senior engineer was helpful, knowledgable and approachable but recently I’ve realised more and more how massive his ego is and how he looks down on people with less experience.
Here’s what happened today:
– In a private chat, he asked me how I even tested and merged my PR when it doesn’t even compile
– I told him that it did compile when i merged it
– He insisted that whatever code was in my PR should not be able to compile
– I showed him receipts of the builds in the pipeline which show that the PR compiled successfully
– He then doubled down and accused me of changing the code after the last successful build because it definitely doesn’t compile now
– Soon after, he realised that the reason the code was not compiling was another dev (A) had created a feature branch from dev at the same time that i created my feature branch
– In my PR, whatever code that dev A was working on did not exist in my branch
– I changed a function signature, compiled, tested, and merged my code
– A week later, dev A merged new code that using the old function, causing it to not compile
– Why dev A did not pull changes from dev after I merged or resolve merge conflicts is beyond me but that is not the point
– Senior engineer came at me demanding why I changed the function signature
– I saidI couldn’t remember why I did, I reviewed my own code and admitted that everything would have worked fine if i hadn’t
– He said that because of this change, i broke dev A’s code
– This pissed me off so much because dev A’s code didn’t even exist at the time of the merge, I had no way of knowing changing a function would break his code in HIS branch
– I defended myself aggressively saying that I shouldn’t be taking responsibility for code breaking
– Senior engineer then said its not about assigning responsibility or blame but about understanding what changing functions that are intended to be shared can cause as we don’t typically pull changes in from dev before merging (?? not sure what he’s talking about here because i definitely make it a point to fetch changes so i can resolve any conflicts early)
– I tried responding professionally by saying that i own the mistake of changing the function without a good reason but that i would appreciate if we can clear misunderstandings of what the mistake was before saying things like i didn’t compile or test my code
– He didn’t take this kindly focusing on the fact that I did in fact change code that resulted in someone else not being able to compile theirs and that he pointed it out so that i understand what can be the consequences of doing such things, at this point i left it as it was cos i was fuming
Anyone in my position receiving accusations like that would have felt like he was definitely trying to assign blame. This isn’t the first time this has happened, he has displayed an enormous sense of superiority to anyone with less experience, even heard him refer to devs in other teams as r*tards for not implementing certain things in a way he deems proper. To make things worse, he’s slated to become my manager before the end of the year and seeing as he doesn’t think highly of me, this could be a serious detriment to my career just as I’m getting started. Anyone has faced a similar situation? Any advice on how to deal with this is appreciated
submitted by /u/bobbledog10
[link] [comments]