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












3















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
    2 hours ago






  • 1





    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
    1 hour 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
    1 hour ago













  • Are you collaborating at all with this senior on this project? Or are you both just doing your own thing?

    – DaveG
    12 mins ago
















3















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
    2 hours ago






  • 1





    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
    1 hour 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
    1 hour ago













  • Are you collaborating at all with this senior on this project? Or are you both just doing your own thing?

    – DaveG
    12 mins ago














3












3








3








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 6 hours ago









RandomDevManRandomDevMan

261




261




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
    2 hours ago






  • 1





    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
    1 hour 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
    1 hour ago













  • Are you collaborating at all with this senior on this project? Or are you both just doing your own thing?

    – DaveG
    12 mins ago














  • 1





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

    – Joe W
    2 hours ago






  • 1





    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
    1 hour 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
    1 hour ago













  • Are you collaborating at all with this senior on this project? Or are you both just doing your own thing?

    – DaveG
    12 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
2 hours ago





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

– Joe W
2 hours ago




1




1





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
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
1 hour 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
1 hour 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
1 hour ago















Are you collaborating at all with this senior on this project? Or are you both just doing your own thing?

– DaveG
12 mins ago





Are you collaborating at all with this senior on this project? Or are you both just doing your own thing?

– DaveG
12 mins ago










4 Answers
4






active

oldest

votes


















10














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
    6 hours ago



















1














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
    2 hours ago











  • Horrible advice. Your job, as a developer, is to write code that solves the company's problems and to help create and support procedures to enable that. How much experience you have doesn't change things- if their practices are bad, you should try to improve them. Now you should definitely be polite, choose your battles, and listen to reasons you may be wrong. But ignore anyone who says you should shut up and deal, they're the people who cause these kinds of messes.

    – Gabe Sechan
    19 mins ago



















1














Often times the best programmers are the ones with the humility to admit when they're wrong and that don't need to hide behind layers of bullshit to cover up for not knowing something






share|improve this answer








New contributor




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




























    0














    Do you currently have the great luck of working in an industry where there's plenty of work.



    Right now you should be working for a company where either a) you love your job or b) you are learning every single day (which will help with a) in the long term). I can see no reason whatsoever for you to remain at this job.





    share























      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: false,
      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




















      StackExchange.ready(function () {
      $("#show-editor-button input, #show-editor-button button").click(function () {
      var showEditor = function() {
      $("#show-editor-button").hide();
      $("#post-form").removeClass("dno");
      StackExchange.editor.finallyInit();
      };

      var useFancy = $(this).data('confirm-use-fancy');
      if(useFancy == 'True') {
      var popupTitle = $(this).data('confirm-fancy-title');
      var popupBody = $(this).data('confirm-fancy-body');
      var popupAccept = $(this).data('confirm-fancy-accept-button');

      $(this).loadPopup({
      url: '/post/self-answer-popup',
      loaded: function(popup) {
      var pTitle = $(popup).find('h2');
      var pBody = $(popup).find('.popup-body');
      var pSubmit = $(popup).find('.popup-submit');

      pTitle.text(popupTitle);
      pBody.html(popupBody);
      pSubmit.val(popupAccept).click(showEditor);
      }
      })
      } else{
      var confirmText = $(this).data('confirm-text');
      if (confirmText ? confirm(confirmText) : true) {
      showEditor();
      }
      }
      });
      });






      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      10














      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
        6 hours ago
















      10














      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
        6 hours ago














      10












      10








      10







      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 6 hours ago









      John R. StrohmJohn R. Strohm

      5,84222025




      5,84222025








      • 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
        6 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
        6 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
      6 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
      6 hours ago













      1














      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
        2 hours ago











      • Horrible advice. Your job, as a developer, is to write code that solves the company's problems and to help create and support procedures to enable that. How much experience you have doesn't change things- if their practices are bad, you should try to improve them. Now you should definitely be polite, choose your battles, and listen to reasons you may be wrong. But ignore anyone who says you should shut up and deal, they're the people who cause these kinds of messes.

        – Gabe Sechan
        19 mins ago
















      1














      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
        2 hours ago











      • Horrible advice. Your job, as a developer, is to write code that solves the company's problems and to help create and support procedures to enable that. How much experience you have doesn't change things- if their practices are bad, you should try to improve them. Now you should definitely be polite, choose your battles, and listen to reasons you may be wrong. But ignore anyone who says you should shut up and deal, they're the people who cause these kinds of messes.

        – Gabe Sechan
        19 mins ago














      1












      1








      1







      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 3 hours ago

























      answered 3 hours ago









      DigitalBlade969DigitalBlade969

      8,1362931




      8,1362931













      • 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
        2 hours ago











      • Horrible advice. Your job, as a developer, is to write code that solves the company's problems and to help create and support procedures to enable that. How much experience you have doesn't change things- if their practices are bad, you should try to improve them. Now you should definitely be polite, choose your battles, and listen to reasons you may be wrong. But ignore anyone who says you should shut up and deal, they're the people who cause these kinds of messes.

        – Gabe Sechan
        19 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
        2 hours ago











      • Horrible advice. Your job, as a developer, is to write code that solves the company's problems and to help create and support procedures to enable that. How much experience you have doesn't change things- if their practices are bad, you should try to improve them. Now you should definitely be polite, choose your battles, and listen to reasons you may be wrong. But ignore anyone who says you should shut up and deal, they're the people who cause these kinds of messes.

        – Gabe Sechan
        19 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
      2 hours 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
      2 hours ago













      Horrible advice. Your job, as a developer, is to write code that solves the company's problems and to help create and support procedures to enable that. How much experience you have doesn't change things- if their practices are bad, you should try to improve them. Now you should definitely be polite, choose your battles, and listen to reasons you may be wrong. But ignore anyone who says you should shut up and deal, they're the people who cause these kinds of messes.

      – Gabe Sechan
      19 mins ago





      Horrible advice. Your job, as a developer, is to write code that solves the company's problems and to help create and support procedures to enable that. How much experience you have doesn't change things- if their practices are bad, you should try to improve them. Now you should definitely be polite, choose your battles, and listen to reasons you may be wrong. But ignore anyone who says you should shut up and deal, they're the people who cause these kinds of messes.

      – Gabe Sechan
      19 mins ago











      1














      Often times the best programmers are the ones with the humility to admit when they're wrong and that don't need to hide behind layers of bullshit to cover up for not knowing something






      share|improve this answer








      New contributor




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

























        1














        Often times the best programmers are the ones with the humility to admit when they're wrong and that don't need to hide behind layers of bullshit to cover up for not knowing something






        share|improve this answer








        New contributor




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























          1












          1








          1







          Often times the best programmers are the ones with the humility to admit when they're wrong and that don't need to hide behind layers of bullshit to cover up for not knowing something






          share|improve this answer








          New contributor




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










          Often times the best programmers are the ones with the humility to admit when they're wrong and that don't need to hide behind layers of bullshit to cover up for not knowing something







          share|improve this answer








          New contributor




          robertmain 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 answer



          share|improve this answer






          New contributor




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









          answered 41 mins ago









          robertmainrobertmain

          111




          111




          New contributor




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





          New contributor





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






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























              0














              Do you currently have the great luck of working in an industry where there's plenty of work.



              Right now you should be working for a company where either a) you love your job or b) you are learning every single day (which will help with a) in the long term). I can see no reason whatsoever for you to remain at this job.





              share




























                0














                Do you currently have the great luck of working in an industry where there's plenty of work.



                Right now you should be working for a company where either a) you love your job or b) you are learning every single day (which will help with a) in the long term). I can see no reason whatsoever for you to remain at this job.





                share


























                  0












                  0








                  0







                  Do you currently have the great luck of working in an industry where there's plenty of work.



                  Right now you should be working for a company where either a) you love your job or b) you are learning every single day (which will help with a) in the long term). I can see no reason whatsoever for you to remain at this job.





                  share













                  Do you currently have the great luck of working in an industry where there's plenty of work.



                  Right now you should be working for a company where either a) you love your job or b) you are learning every single day (which will help with a) in the long term). I can see no reason whatsoever for you to remain at this job.






                  share











                  share


                  share










                  answered 9 mins ago









                  bnielandbnieland

                  2214




                  2214






















                      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

                      Ponta tanko

                      Tantalo (mitologio)

                      Franz Schubert