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

Just to add; my expectation for Juniors would be:

• Complete very simple work unaided, given adequate instructions
• Complete moderate complexity work with help (pair-coding)

My training scheme for juniors on medium complexity work is:

1. You watch me build it (I'm driving the screen and thinking out loud about design choices)
2. I help you build it (You're driving and I'm doing a mix of leading questions and literally telling you what to type -- this develops muscle memory)
3. I watch you build it (You're driving and thinking out loud and I tell you when you're not quite right)
4. You build it on your own and ask for help if necessary

We gotta set juniors up to succeed. This means plenty of training wheels, lots of written instructions, and a conscious mentoring program like the above!