Code reviews are a great way to learn by example, and another good way of skillbuilding for the author by teaching. I like to think that, suppose someone more senior wrote something overly complex. You could either ask about it to which they try to clearly explain, or maybe you interpret it as 'better' code, and you mimic the style which they later critique. You could then both go back to the original and distil it and wind up improving both pieces. Really nice post.
Yup! That's exactly how my experience went. I think It's important for senior devs to instil this (and other mindsets) into junior devs as they come aboard in an organization. It's often the most obvious things that are the most essential for doing good work, but since they're so seemingly obvious they are rarely ever taught. For onboarding junior devs, sometimes stating the obvious is just what's needed.
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.
Code reviews are a great way to learn by example, and another good way of skillbuilding for the author by teaching. I like to think that, suppose someone more senior wrote something overly complex. You could either ask about it to which they try to clearly explain, or maybe you interpret it as 'better' code, and you mimic the style which they later critique. You could then both go back to the original and distil it and wind up improving both pieces. Really nice post.
Yup! That's exactly how my experience went. I think It's important for senior devs to instil this (and other mindsets) into junior devs as they come aboard in an organization. It's often the most obvious things that are the most essential for doing good work, but since they're so seemingly obvious they are rarely ever taught. For onboarding junior devs, sometimes stating the obvious is just what's needed.