Sometimes it takes a little unintentional embarrassment to drive a point home. It’ll make them think twice next time.

What I mean by that is that as long as you’re not intentionally or maliciously trying to embarrass them, then you shouldn’t feel bad. You cannot always control how somebody receives information; nor should you. The best you can do is to be clear and polite in your communication. If someone’s feelings get hurt, that’s on them to reconcile, not you.

This is genuinely like parenting a child: they need to develop their critical thinking skills, and to gain their own confidence. So they must be left to make their own mistakes to learn from. Your job is to give show them the tools to use, give advice when necessary, and be there to catch them when they fall; because they will fall.

Doing this will help bolster their self-confidence and make them better mid-/senior-developers later in their career. Coddling them and constantly holding their hand will make them reliant on other people and prevent them from learning anything.

Edit: also remember KISS. 😊

I see coding tasks with juniors a way to actually have a two-way conversation with said juniors and get them engaging.

What I tend to do is I'll give them an objective, and then I'll ask them what they think needs to be done. Each step of the way I'll try and correct them and get them going in the right direction.

If all is well, everything is cleared up, the junior knows what to do at each step, and then they go off and do it. Then I do the code review and the conversation restarts.

More often than not, the junior dev will get mentally stuck on a problem that they cannot conceptualise. That's fine - I tell them to leave it, work on the stuff they can do, and then we'll tackle it together.

Generally speaking, good junior devs can conceptualise a task about 50-80% and will get stuck on the other 20-50%. An excellent junior dev can be given a task and independently complete it - the code may not be perfect or up to a middle-senior coding quality, but they can get the job done.

The bad junior developers are the ones who need their hands held at every step of the way and never seem to improve or improve at such a snails pace that it is taking effective resources away from the team (i.e. senior devs - 1 or more) to explain the task repeatedly.

At this point, you need to raise that up to your line manager and have a serious discussion about whether you and your line manager think it is worth the investment to keep teaching this person while making said line manager aware of the problems (and make this based with facts that both you and the line manager can clearly observe and/or have observed).

For the others, you should go from a path of having to explain fundamental concepts (mostly because you both missed out on the weird edge cases of the task at hand) to in months being able to leave said juniors to the task and have them mostly complete it without any help from senior devs. And seeing that progress is why mentoring & code reviews is great - seeing that personal development in real time is an incredibly rewarding feeling.

Completely understand the frustration here. Mistakes happen, even competent people sincerely trying to do a good job can overlook things, etc. But if it's a pattern of just copying and pasting code without really even trying to understand what it does, that's a big problem that needs to be addressed. And frankly they should feel embarrassed if it happens more than once or twice.

OTOH, delivering criticism in a way that winds up productive for all involved is difficult at best, and the outcome depends on the junior as much as it does the senior. What good is being right if it ultimately just alienates you from your team? Tough situation for sure, and one of the many reasons it's so important to hire carefully (which is itself a whole huge can of worms too!).

Can you simply ask them to walk through their submission line by line with you, explaining what it's doing? If you've never asked that before it might come across as a strange request, but if you phrase it well it's possible this causes them to notice their poor understanding without you ever seeming to point it out.

And you guessed it, they copied that ignored-annotation, too, complete with the comment "//TODO currently broken". The test they implemented was not run, not even once.

Junior dev here, this is the kind of stuff that is supposed to prompt you to ask questions. Literally one slack message when you see it, and give it a few hours for whenever you have time to see it and respond. I know it's annoying messaging y'all with stuff but... C'mon you gotta do it sometimes, especially if it's something you can reasonably predict will come up in review or is a simple question that doesn't require a lot of time to answer.

This is still a good practice to find out who is actually working and who is thinking Zero-effort copy&paste will do.

I'd much rather praise them when they do something well, but this is so hard to spot when just reading over committed code. All the obstacles they cleared are not visible in there.

This is SO true and exactly why code reviews always feel like a beat down (even when they're not). There's no visibility into the truly good work that's already been done.

It's even worse when you can tell they really tried and still end up with spaghetti. Even mid- to senior developers do this. Rhe more senior they ~~claim to be~~ are, the more embarrasing when you have to get the stick.

Some people try to be so clever with fancy design patterns or bit-tricks, instead of just solving the problem, you now have two problems and a solution to one of them.

Now you have all right to motivate your mate fixing their code. HF with the stick!

We have two sticks and a rock for the whole platoon.

What is this "code freeze" you speak of? Every commit goes straight to prod!