Thank you, your point is the exact one I argue against in my post, which makes me happy I wrote it. No, junior developer reviews AND approvals are not a waste of time. If your code can’t be understood by a junior, it shouldn’t be considered as good enough to be merged.
back
1 comments
I'm all in favor of junior developer reviews and approvals. I completely agree that if they can't understand the code, it's frequently a problem with the code. I'm against rubber stamps, where there's no evidence that they've engaged with it. Unfortunately that's the rule rather than the exception in my current environment. If e.g. a developer hasn't made a comment in dozens of reviews, and just returns an approval in a few minutes, junior or not it's a problem. My code isn't that good. Here, it's an epidemic among the juniors.
On this point I agree with you. And in my experience, it happens as often with seniors as with juniors. The famous “LGTM” on a 1000-line PR ;)