Mixing
How to survive as a junior developer in workplace that does not tolerate mistakes
Clash 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?
company-culture teamwork training junior review
asked 4 mins ago
Bbbbbbbbbb
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.
add a comment |Â
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?
company-culture teamwork training junior review
asked 4 mins ago
Bbbbbbbbbb
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.
add a comment |Â
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?
company-culture teamwork training junior review
asked 4 mins ago
Bbbbbbbbbb
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.
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
company-culture teamwork training junior review
asked 4 mins ago
Bbbbbbbbbb
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.
asked 4 mins ago
Bbbbbbbbbb
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.
asked 4 mins ago
Bbbbbbbbbb
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.
asked 4 mins ago
Bbbbbbbbbb
1
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.
add a comment |Â
add a comment |Â
active
oldest
votes
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.
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
