DEV Community

Discussion on: How to tell a Junior Dev that what they've done is wrong?

Collapse
 
preciouschicken profile image
Precious Chicken

Kind of tactical but when you are actually delivering the constructive criticism you could sandwich it: so make a positive statement (e.g. you're doing great work on x), the key negative statement (e.g. but you could do y differently) and end with another positive statement (e.g. you're proving a great fit with team z). This obviously has to be sincere / genuine; but hopefully they take onboard what they need to do better while still feeling ok about things. After all most people want to go to work and do a good job.

Of course if you've got nothing at all positive to say, you've got a different problem...

Collapse
 
nombrekeff profile image
Keff

Excelent addition, this is one I already apply, as I value it when the same is done to me. We, as humans, tend to focus on the negatives and not the positives.