Co-worker sabotaging/undoing my work. (Software Development)












2















Context:
I just got hired as a software developer in a team which has freshly transitioned from networking to development. Before me they hired another developer a year ago who has been since then given a senior role, he is the only other developer by background in that team. This senior dev and I have graduated from same college and program as well, and this is also our both first job, only difference being he graduated from college before me being older than me. I am saying this to explain how much of a difference he and I have in professional experience.
Our manager is not technical, therefore he is one of those "I care about how much money did it save the company."



Problem:
Because of him being the only dev in the team for more than a year, no one challenged his opinions and ideas on how processes should work. When I joined the team, I saw a team not using Git/GitHub correctly or straight up not using it, no documentation, pushing code directly to production boxes, no collaboration, manual if some testing. (Things are not that bad, the team is learning and they realized they aren't following the best practices.)



When I joined, as in any other team, I started putting my ideas forward, but I am always met with a condescending response ("Do you even know insert given topic") by this senior dev. The rest of the team & manager just side with senior, when I asked them why, the conversation went somewhat like this:



Me: Why do you think this is okay?



Team & manager: He is senior and he knows more.



Me: Why do you think he knows more?



Team & manager: Dude, he uses Linux as his dev environment, he knows a lot.



(That Linux comment actually happened.)



So, I decided to stop getting myself insulted and just do my own thing until maybe more developers are hired and/or we get a technical manager. However, recently I was told to collaborate with this senior on a project, as usual he denied my ideas...which was okay, I decided to play by his rules(not worth my time) until I recently saw my branches and commits being deleted because he had something else in plan, which was not communicated to anyone.



I am still on probation and don't want to cause a drama but it's getting hard not to.










share|improve this question







New contributor




RandomDevMan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    How do you become a senior developer with 1 year of experience? That alone sounds like a red flag.

    – Joe W
    1 hour ago











  • You are catching close votes. I am inclined to agree with them. What is your goal? Can you state it clearly? Otherwise this is just a rant.

    – bruglesco
    35 mins ago











  • Welcome to software development. There are a lot of people like this out there - they use a lot of words to obfuscate that they're not good programmers. Just be aware that there are a lot of good programmers out there too. The trick I think, is to use the interview as your chance to test the quality of the tech lead/senior you're working under. Ask them some technical questions.

    – dwjohnston
    15 mins ago


















2















Context:
I just got hired as a software developer in a team which has freshly transitioned from networking to development. Before me they hired another developer a year ago who has been since then given a senior role, he is the only other developer by background in that team. This senior dev and I have graduated from same college and program as well, and this is also our both first job, only difference being he graduated from college before me being older than me. I am saying this to explain how much of a difference he and I have in professional experience.
Our manager is not technical, therefore he is one of those "I care about how much money did it save the company."



Problem:
Because of him being the only dev in the team for more than a year, no one challenged his opinions and ideas on how processes should work. When I joined the team, I saw a team not using Git/GitHub correctly or straight up not using it, no documentation, pushing code directly to production boxes, no collaboration, manual if some testing. (Things are not that bad, the team is learning and they realized they aren't following the best practices.)



When I joined, as in any other team, I started putting my ideas forward, but I am always met with a condescending response ("Do you even know insert given topic") by this senior dev. The rest of the team & manager just side with senior, when I asked them why, the conversation went somewhat like this:



Me: Why do you think this is okay?



Team & manager: He is senior and he knows more.



Me: Why do you think he knows more?



Team & manager: Dude, he uses Linux as his dev environment, he knows a lot.



(That Linux comment actually happened.)



So, I decided to stop getting myself insulted and just do my own thing until maybe more developers are hired and/or we get a technical manager. However, recently I was told to collaborate with this senior on a project, as usual he denied my ideas...which was okay, I decided to play by his rules(not worth my time) until I recently saw my branches and commits being deleted because he had something else in plan, which was not communicated to anyone.



I am still on probation and don't want to cause a drama but it's getting hard not to.










share|improve this question







New contributor




RandomDevMan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    How do you become a senior developer with 1 year of experience? That alone sounds like a red flag.

    – Joe W
    1 hour ago











  • You are catching close votes. I am inclined to agree with them. What is your goal? Can you state it clearly? Otherwise this is just a rant.

    – bruglesco
    35 mins ago











  • Welcome to software development. There are a lot of people like this out there - they use a lot of words to obfuscate that they're not good programmers. Just be aware that there are a lot of good programmers out there too. The trick I think, is to use the interview as your chance to test the quality of the tech lead/senior you're working under. Ask them some technical questions.

    – dwjohnston
    15 mins ago
















2












2








2








Context:
I just got hired as a software developer in a team which has freshly transitioned from networking to development. Before me they hired another developer a year ago who has been since then given a senior role, he is the only other developer by background in that team. This senior dev and I have graduated from same college and program as well, and this is also our both first job, only difference being he graduated from college before me being older than me. I am saying this to explain how much of a difference he and I have in professional experience.
Our manager is not technical, therefore he is one of those "I care about how much money did it save the company."



Problem:
Because of him being the only dev in the team for more than a year, no one challenged his opinions and ideas on how processes should work. When I joined the team, I saw a team not using Git/GitHub correctly or straight up not using it, no documentation, pushing code directly to production boxes, no collaboration, manual if some testing. (Things are not that bad, the team is learning and they realized they aren't following the best practices.)



When I joined, as in any other team, I started putting my ideas forward, but I am always met with a condescending response ("Do you even know insert given topic") by this senior dev. The rest of the team & manager just side with senior, when I asked them why, the conversation went somewhat like this:



Me: Why do you think this is okay?



Team & manager: He is senior and he knows more.



Me: Why do you think he knows more?



Team & manager: Dude, he uses Linux as his dev environment, he knows a lot.



(That Linux comment actually happened.)



So, I decided to stop getting myself insulted and just do my own thing until maybe more developers are hired and/or we get a technical manager. However, recently I was told to collaborate with this senior on a project, as usual he denied my ideas...which was okay, I decided to play by his rules(not worth my time) until I recently saw my branches and commits being deleted because he had something else in plan, which was not communicated to anyone.



I am still on probation and don't want to cause a drama but it's getting hard not to.










share|improve this question







New contributor




RandomDevMan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












Context:
I just got hired as a software developer in a team which has freshly transitioned from networking to development. Before me they hired another developer a year ago who has been since then given a senior role, he is the only other developer by background in that team. This senior dev and I have graduated from same college and program as well, and this is also our both first job, only difference being he graduated from college before me being older than me. I am saying this to explain how much of a difference he and I have in professional experience.
Our manager is not technical, therefore he is one of those "I care about how much money did it save the company."



Problem:
Because of him being the only dev in the team for more than a year, no one challenged his opinions and ideas on how processes should work. When I joined the team, I saw a team not using Git/GitHub correctly or straight up not using it, no documentation, pushing code directly to production boxes, no collaboration, manual if some testing. (Things are not that bad, the team is learning and they realized they aren't following the best practices.)



When I joined, as in any other team, I started putting my ideas forward, but I am always met with a condescending response ("Do you even know insert given topic") by this senior dev. The rest of the team & manager just side with senior, when I asked them why, the conversation went somewhat like this:



Me: Why do you think this is okay?



Team & manager: He is senior and he knows more.



Me: Why do you think he knows more?



Team & manager: Dude, he uses Linux as his dev environment, he knows a lot.



(That Linux comment actually happened.)



So, I decided to stop getting myself insulted and just do my own thing until maybe more developers are hired and/or we get a technical manager. However, recently I was told to collaborate with this senior on a project, as usual he denied my ideas...which was okay, I decided to play by his rules(not worth my time) until I recently saw my branches and commits being deleted because he had something else in plan, which was not communicated to anyone.



I am still on probation and don't want to cause a drama but it's getting hard not to.







software-industry software-development






share|improve this question







New contributor




RandomDevMan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




RandomDevMan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




RandomDevMan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 5 hours ago









RandomDevManRandomDevMan

211




211




New contributor




RandomDevMan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





RandomDevMan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






RandomDevMan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1





    How do you become a senior developer with 1 year of experience? That alone sounds like a red flag.

    – Joe W
    1 hour ago











  • You are catching close votes. I am inclined to agree with them. What is your goal? Can you state it clearly? Otherwise this is just a rant.

    – bruglesco
    35 mins ago











  • Welcome to software development. There are a lot of people like this out there - they use a lot of words to obfuscate that they're not good programmers. Just be aware that there are a lot of good programmers out there too. The trick I think, is to use the interview as your chance to test the quality of the tech lead/senior you're working under. Ask them some technical questions.

    – dwjohnston
    15 mins ago
















  • 1





    How do you become a senior developer with 1 year of experience? That alone sounds like a red flag.

    – Joe W
    1 hour ago











  • You are catching close votes. I am inclined to agree with them. What is your goal? Can you state it clearly? Otherwise this is just a rant.

    – bruglesco
    35 mins ago











  • Welcome to software development. There are a lot of people like this out there - they use a lot of words to obfuscate that they're not good programmers. Just be aware that there are a lot of good programmers out there too. The trick I think, is to use the interview as your chance to test the quality of the tech lead/senior you're working under. Ask them some technical questions.

    – dwjohnston
    15 mins ago










1




1





How do you become a senior developer with 1 year of experience? That alone sounds like a red flag.

– Joe W
1 hour ago





How do you become a senior developer with 1 year of experience? That alone sounds like a red flag.

– Joe W
1 hour ago













You are catching close votes. I am inclined to agree with them. What is your goal? Can you state it clearly? Otherwise this is just a rant.

– bruglesco
35 mins ago





You are catching close votes. I am inclined to agree with them. What is your goal? Can you state it clearly? Otherwise this is just a rant.

– bruglesco
35 mins ago













Welcome to software development. There are a lot of people like this out there - they use a lot of words to obfuscate that they're not good programmers. Just be aware that there are a lot of good programmers out there too. The trick I think, is to use the interview as your chance to test the quality of the tech lead/senior you're working under. Ask them some technical questions.

– dwjohnston
15 mins ago







Welcome to software development. There are a lot of people like this out there - they use a lot of words to obfuscate that they're not good programmers. Just be aware that there are a lot of good programmers out there too. The trick I think, is to use the interview as your chance to test the quality of the tech lead/senior you're working under. Ask them some technical questions.

– dwjohnston
15 mins ago












2 Answers
2






active

oldest

votes


















8














There was a time when I would have said "Stick it out, give things a chance."



That was then and this is now.



I've been where you are. What the "senior" did is unacceptable. Pulling your commits is marginally justifiable, if he IMMEDIATELY issues his design plan document. Deleting your (presumably private) branches is not.



Get out of there. As soon as possible.






share|improve this answer



















  • 3





    The way that "senior" is behaving made me want to write the same thing about getting out. I worked with one guy and it was an absolute dream - we discussed, put forward ideas : some of mine got accepted, some weren't... but *all were looked at as to how they "fit" and how they worked towards the future... Plus 1 from me, said it better than I could.

    – Solar Mike
    4 hours ago



















2














You made the mistake so many make.



You came straight from school to your first job and took it upon you to change how the company works.



Nobody cares if your suggestions are good or not, they just see a still green behind the ears graduate who thinks he knows better than everyone before him.



Of course you'll be met with resistance and looked down upon.



So that was why you're in the situation you're in right now.



Your senior either understood you know more than him and views you as a danger to his position or he thinks you're an immature, know it all hack who can't write correct code.



You have two options:



Confront or submit.



If you confront ask why your work was deleted and escalate to superiors if you can prove it was replaced by inferior code.



Be prepared for backlash up to the point that you want to or are forced to look for a new job.



If you submit, just do your tasks and bite your tongue if you have an idea how to optimize the company.



It's not your place until asked to do so, given a position with that responsibility or have your own company that you can run exactly the way you want it to...






share|improve this answer


























  • There are situations where it's appropriate to suggest changes straight out of school. If the company specifically requests suggestions, it may be welcome. If the company sings the praises of the prior FNG who's still on probation, for the changes to the company they proposed - but in this case be extra careful to not step on toes.

    – Ed Grimm
    53 mins ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






RandomDevMan is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f130065%2fco-worker-sabotaging-undoing-my-work-software-development%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









8














There was a time when I would have said "Stick it out, give things a chance."



That was then and this is now.



I've been where you are. What the "senior" did is unacceptable. Pulling your commits is marginally justifiable, if he IMMEDIATELY issues his design plan document. Deleting your (presumably private) branches is not.



Get out of there. As soon as possible.






share|improve this answer



















  • 3





    The way that "senior" is behaving made me want to write the same thing about getting out. I worked with one guy and it was an absolute dream - we discussed, put forward ideas : some of mine got accepted, some weren't... but *all were looked at as to how they "fit" and how they worked towards the future... Plus 1 from me, said it better than I could.

    – Solar Mike
    4 hours ago
















8














There was a time when I would have said "Stick it out, give things a chance."



That was then and this is now.



I've been where you are. What the "senior" did is unacceptable. Pulling your commits is marginally justifiable, if he IMMEDIATELY issues his design plan document. Deleting your (presumably private) branches is not.



Get out of there. As soon as possible.






share|improve this answer



















  • 3





    The way that "senior" is behaving made me want to write the same thing about getting out. I worked with one guy and it was an absolute dream - we discussed, put forward ideas : some of mine got accepted, some weren't... but *all were looked at as to how they "fit" and how they worked towards the future... Plus 1 from me, said it better than I could.

    – Solar Mike
    4 hours ago














8












8








8







There was a time when I would have said "Stick it out, give things a chance."



That was then and this is now.



I've been where you are. What the "senior" did is unacceptable. Pulling your commits is marginally justifiable, if he IMMEDIATELY issues his design plan document. Deleting your (presumably private) branches is not.



Get out of there. As soon as possible.






share|improve this answer













There was a time when I would have said "Stick it out, give things a chance."



That was then and this is now.



I've been where you are. What the "senior" did is unacceptable. Pulling your commits is marginally justifiable, if he IMMEDIATELY issues his design plan document. Deleting your (presumably private) branches is not.



Get out of there. As soon as possible.







share|improve this answer












share|improve this answer



share|improve this answer










answered 4 hours ago









John R. StrohmJohn R. Strohm

5,82222024




5,82222024








  • 3





    The way that "senior" is behaving made me want to write the same thing about getting out. I worked with one guy and it was an absolute dream - we discussed, put forward ideas : some of mine got accepted, some weren't... but *all were looked at as to how they "fit" and how they worked towards the future... Plus 1 from me, said it better than I could.

    – Solar Mike
    4 hours ago














  • 3





    The way that "senior" is behaving made me want to write the same thing about getting out. I worked with one guy and it was an absolute dream - we discussed, put forward ideas : some of mine got accepted, some weren't... but *all were looked at as to how they "fit" and how they worked towards the future... Plus 1 from me, said it better than I could.

    – Solar Mike
    4 hours ago








3




3





The way that "senior" is behaving made me want to write the same thing about getting out. I worked with one guy and it was an absolute dream - we discussed, put forward ideas : some of mine got accepted, some weren't... but *all were looked at as to how they "fit" and how they worked towards the future... Plus 1 from me, said it better than I could.

– Solar Mike
4 hours ago





The way that "senior" is behaving made me want to write the same thing about getting out. I worked with one guy and it was an absolute dream - we discussed, put forward ideas : some of mine got accepted, some weren't... but *all were looked at as to how they "fit" and how they worked towards the future... Plus 1 from me, said it better than I could.

– Solar Mike
4 hours ago













2














You made the mistake so many make.



You came straight from school to your first job and took it upon you to change how the company works.



Nobody cares if your suggestions are good or not, they just see a still green behind the ears graduate who thinks he knows better than everyone before him.



Of course you'll be met with resistance and looked down upon.



So that was why you're in the situation you're in right now.



Your senior either understood you know more than him and views you as a danger to his position or he thinks you're an immature, know it all hack who can't write correct code.



You have two options:



Confront or submit.



If you confront ask why your work was deleted and escalate to superiors if you can prove it was replaced by inferior code.



Be prepared for backlash up to the point that you want to or are forced to look for a new job.



If you submit, just do your tasks and bite your tongue if you have an idea how to optimize the company.



It's not your place until asked to do so, given a position with that responsibility or have your own company that you can run exactly the way you want it to...






share|improve this answer


























  • There are situations where it's appropriate to suggest changes straight out of school. If the company specifically requests suggestions, it may be welcome. If the company sings the praises of the prior FNG who's still on probation, for the changes to the company they proposed - but in this case be extra careful to not step on toes.

    – Ed Grimm
    53 mins ago
















2














You made the mistake so many make.



You came straight from school to your first job and took it upon you to change how the company works.



Nobody cares if your suggestions are good or not, they just see a still green behind the ears graduate who thinks he knows better than everyone before him.



Of course you'll be met with resistance and looked down upon.



So that was why you're in the situation you're in right now.



Your senior either understood you know more than him and views you as a danger to his position or he thinks you're an immature, know it all hack who can't write correct code.



You have two options:



Confront or submit.



If you confront ask why your work was deleted and escalate to superiors if you can prove it was replaced by inferior code.



Be prepared for backlash up to the point that you want to or are forced to look for a new job.



If you submit, just do your tasks and bite your tongue if you have an idea how to optimize the company.



It's not your place until asked to do so, given a position with that responsibility or have your own company that you can run exactly the way you want it to...






share|improve this answer


























  • There are situations where it's appropriate to suggest changes straight out of school. If the company specifically requests suggestions, it may be welcome. If the company sings the praises of the prior FNG who's still on probation, for the changes to the company they proposed - but in this case be extra careful to not step on toes.

    – Ed Grimm
    53 mins ago














2












2








2







You made the mistake so many make.



You came straight from school to your first job and took it upon you to change how the company works.



Nobody cares if your suggestions are good or not, they just see a still green behind the ears graduate who thinks he knows better than everyone before him.



Of course you'll be met with resistance and looked down upon.



So that was why you're in the situation you're in right now.



Your senior either understood you know more than him and views you as a danger to his position or he thinks you're an immature, know it all hack who can't write correct code.



You have two options:



Confront or submit.



If you confront ask why your work was deleted and escalate to superiors if you can prove it was replaced by inferior code.



Be prepared for backlash up to the point that you want to or are forced to look for a new job.



If you submit, just do your tasks and bite your tongue if you have an idea how to optimize the company.



It's not your place until asked to do so, given a position with that responsibility or have your own company that you can run exactly the way you want it to...






share|improve this answer















You made the mistake so many make.



You came straight from school to your first job and took it upon you to change how the company works.



Nobody cares if your suggestions are good or not, they just see a still green behind the ears graduate who thinks he knows better than everyone before him.



Of course you'll be met with resistance and looked down upon.



So that was why you're in the situation you're in right now.



Your senior either understood you know more than him and views you as a danger to his position or he thinks you're an immature, know it all hack who can't write correct code.



You have two options:



Confront or submit.



If you confront ask why your work was deleted and escalate to superiors if you can prove it was replaced by inferior code.



Be prepared for backlash up to the point that you want to or are forced to look for a new job.



If you submit, just do your tasks and bite your tongue if you have an idea how to optimize the company.



It's not your place until asked to do so, given a position with that responsibility or have your own company that you can run exactly the way you want it to...







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 hours ago

























answered 2 hours ago









DigitalBlade969DigitalBlade969

8,1102931




8,1102931













  • There are situations where it's appropriate to suggest changes straight out of school. If the company specifically requests suggestions, it may be welcome. If the company sings the praises of the prior FNG who's still on probation, for the changes to the company they proposed - but in this case be extra careful to not step on toes.

    – Ed Grimm
    53 mins ago



















  • There are situations where it's appropriate to suggest changes straight out of school. If the company specifically requests suggestions, it may be welcome. If the company sings the praises of the prior FNG who's still on probation, for the changes to the company they proposed - but in this case be extra careful to not step on toes.

    – Ed Grimm
    53 mins ago

















There are situations where it's appropriate to suggest changes straight out of school. If the company specifically requests suggestions, it may be welcome. If the company sings the praises of the prior FNG who's still on probation, for the changes to the company they proposed - but in this case be extra careful to not step on toes.

– Ed Grimm
53 mins ago





There are situations where it's appropriate to suggest changes straight out of school. If the company specifically requests suggestions, it may be welcome. If the company sings the praises of the prior FNG who's still on probation, for the changes to the company they proposed - but in this case be extra careful to not step on toes.

– Ed Grimm
53 mins ago










RandomDevMan is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















RandomDevMan is a new contributor. Be nice, and check out our Code of Conduct.













RandomDevMan is a new contributor. Be nice, and check out our Code of Conduct.












RandomDevMan is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to The Workplace Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f130065%2fco-worker-sabotaging-undoing-my-work-software-development%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

SQL Server 17 - Attemping to backup to remote NAS but Access is denied

Always On Availability groups resolving state after failover - Remote harden of transaction...

Restoring from pg_dump with foreign key constraints