Code Review: Who should be involved in a peer code review?

Code Review: Who should be involved in a peer code review?
A peer code review involves another developer on the same team (peer), regardless of seniority. A junior developer can learn while reviewing a senior developer’s code and can still have good insights to add.

Quote:
“Code reviews can have more-extensive benefits for a development team. When a junior developer has to review a senior developer, it’s a learning process for both developers. “ The junior developer can learn from reviewing code with a more experienced person,” says D’Souza. “At the same time, when you’re a senior developer and you have to explain your own work, the light bulb might go on that your solution isn’t as solid as you thought.”
– Martin D’Souza

Application:
When selecting a person to perform a code review on your code, you should submit your request to your project team. If you notice that the same person reviews your code each time, request a different reviewer, as you will want to get a mix of feedback over time to grow your skills and to get a fresh perspective.

References:
http://www.oracle.com/technetwork/issue-archive/2013/13-jan/o13upclose-1886634.html

About Chris VanHoose

Principal Software Architect at CT Lien Solutions
This entry was posted in Software Architecture and tagged , . Bookmark the permalink.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.