How to survive as a junior developer in workplace that does not tolerate mistakes

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
0
down vote

favorite












My friend is a junior at a workplace that requires staff to take 100% responsibility for their work. In practice this means no code reviews. Any errors, mistakes or inefficiencies are to be identified yourself.



While staff are encouraged to ask for help when they run into problems, you don't know what you don't know, and my friend is often disciplined by seniors when their work doesn't fit their expectations at the end of a project. This is the cause of a lot of stress for the junior in question and is destroying any confidence they have in their own work.



While I can see the merits of having a "get it right the first time" culture in a workplace full of senior developers, it seems like a hostile work environment for juniors who genuinely don't know any better.



Can anybody suggest techniques for reviewing and error checking your own work? Or alternatively, strategies for cultivating a healthy "learn by mistakes" review culture in a workplace?









share







New contributor




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

























    up vote
    0
    down vote

    favorite












    My friend is a junior at a workplace that requires staff to take 100% responsibility for their work. In practice this means no code reviews. Any errors, mistakes or inefficiencies are to be identified yourself.



    While staff are encouraged to ask for help when they run into problems, you don't know what you don't know, and my friend is often disciplined by seniors when their work doesn't fit their expectations at the end of a project. This is the cause of a lot of stress for the junior in question and is destroying any confidence they have in their own work.



    While I can see the merits of having a "get it right the first time" culture in a workplace full of senior developers, it seems like a hostile work environment for juniors who genuinely don't know any better.



    Can anybody suggest techniques for reviewing and error checking your own work? Or alternatively, strategies for cultivating a healthy "learn by mistakes" review culture in a workplace?









    share







    New contributor




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





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      My friend is a junior at a workplace that requires staff to take 100% responsibility for their work. In practice this means no code reviews. Any errors, mistakes or inefficiencies are to be identified yourself.



      While staff are encouraged to ask for help when they run into problems, you don't know what you don't know, and my friend is often disciplined by seniors when their work doesn't fit their expectations at the end of a project. This is the cause of a lot of stress for the junior in question and is destroying any confidence they have in their own work.



      While I can see the merits of having a "get it right the first time" culture in a workplace full of senior developers, it seems like a hostile work environment for juniors who genuinely don't know any better.



      Can anybody suggest techniques for reviewing and error checking your own work? Or alternatively, strategies for cultivating a healthy "learn by mistakes" review culture in a workplace?









      share







      New contributor




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











      My friend is a junior at a workplace that requires staff to take 100% responsibility for their work. In practice this means no code reviews. Any errors, mistakes or inefficiencies are to be identified yourself.



      While staff are encouraged to ask for help when they run into problems, you don't know what you don't know, and my friend is often disciplined by seniors when their work doesn't fit their expectations at the end of a project. This is the cause of a lot of stress for the junior in question and is destroying any confidence they have in their own work.



      While I can see the merits of having a "get it right the first time" culture in a workplace full of senior developers, it seems like a hostile work environment for juniors who genuinely don't know any better.



      Can anybody suggest techniques for reviewing and error checking your own work? Or alternatively, strategies for cultivating a healthy "learn by mistakes" review culture in a workplace?







      company-culture teamwork training junior review





      share







      New contributor




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










      share







      New contributor




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








      share



      share






      New contributor




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









      asked 4 mins ago









      Bbbbbbbbbb

      1




      1




      New contributor




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





      New contributor





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






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

























          active

          oldest

          votes











          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',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          noCode: true, onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );






          Bbbbbbbbbb 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%2f120224%2fhow-to-survive-as-a-junior-developer-in-workplace-that-does-not-tolerate-mistake%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








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









           

          draft saved


          draft discarded


















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












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











          Bbbbbbbbbb 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%2f120224%2fhow-to-survive-as-a-junior-developer-in-workplace-that-does-not-tolerate-mistake%23new-answer', 'question_page');

          );

          Post as a guest













































































          Comments

          Popular posts from this blog

          What does second last employer means? [closed]

          Installing NextGIS Connect into QGIS 3?

          One-line joke