For me it is different. I do not like correcting people. When we had pod meetings in my school we would do group coding. Sometimes one of the group members would start coding and make blatant errors, but for some reason I would feel bad for correcting them. I guess I didn’t want to make anyone feel bad. I would just let someone else call it out or see if they catch it first
Definitely don't like making people feel bad, but at work feeling sometimes have to come second. I have had several instances if I didn't say something we would be stuck at a problem while on a tight schedule.
I'd say generally it's better to speak out on something than not, at least it means you are paying attention to the topic.
I've let a lot of thing pass by unsaid with my product manager as well. he often asserts why there is a problem with our app even though he doesn't spend time coding the app.
I just let him say whatever he wants because most of the time what he says have zero ramification and it's really not worth busting his chops.
The concept of pair programming actually depends on one person questioning the other, catching each others errors, and offering opinions as a means of increasing quality.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For me it is different. I do not like correcting people. When we had pod meetings in my school we would do group coding. Sometimes one of the group members would start coding and make blatant errors, but for some reason I would feel bad for correcting them. I guess I didn’t want to make anyone feel bad. I would just let someone else call it out or see if they catch it first
Definitely don't like making people feel bad, but at work feeling sometimes have to come second. I have had several instances if I didn't say something we would be stuck at a problem while on a tight schedule.
I'd say generally it's better to speak out on something than not, at least it means you are paying attention to the topic.
I can definitely understand that. I guess it’s different for me because I haven’t been in the work setting yet
I've let a lot of thing pass by unsaid with my product manager as well. he often asserts why there is a problem with our app even though he doesn't spend time coding the app.
I just let him say whatever he wants because most of the time what he says have zero ramification and it's really not worth busting his chops.
The concept of pair programming actually depends on one person questioning the other, catching each others errors, and offering opinions as a means of increasing quality.