Interesting article. To encourage and facilitate these code review conversations, I recommend utilizing a tool like Pullpo.io (<a href="https://pullpo.io/products/channels" rel="nofollow noreferrer">https://pullpo.io/products/channels</a>), It allows all members of the development team to have more enriching code reviews quickly on Slack, so junior developers are encouraged to contribute and grow.<p>As you said in the article, participating in code reviews is an opportunity for growth in countless ways. Junior developers should feel encouraged to partake and positively impact the team.
Dear junior developers, a rubber stamp code review is a waste of your time and mine, and since it counts as an approval in the build integration, it makes the code and product worse by taking the place of a real review.<p>Please instead flag things you don't understand and ask for an explanation. It's worth a senior developer's time to think about it, and either provide some useful training, or more often than they might be comfortable with, ask themselves some hard questions. Your fresh "junior" eyes are a feature as often as a bug, and see things that the seniors don't anymore.<p>I'd much rather have a junior give me a code review with, uh, less sophisticated criticisms, than one that assumes I know what I'm doing. It's at least a sign that they have paid attention.