Are Peer reviews commonly accepted as a value-added practice among the IT-Community? They should be an essential part of the software development cycle, but are usually neglected due to short development sprints, static code analysis, or …
Most of the programmers, (myself included), that have a look into their early code can’t believe the kind of mistakes they made. Even though the code works, most of them would refactor the whole thing, or use a different technology altogether.
On the job, people are expected to learn from copy&paste examples. Not asking questions is a sign of ingenuity. If you have luck, a senior member of the team leads the way.
There are countless quality assurance benefits from Peer Reviews, but I’m going to focus on some hidden factors.
Do You Know What You Are Missing?
1 A peer review is an opportunity to evaluate objectively
If a program has zero defects and is delivered on schedule, it doesn’t mean that the best approach was taken or that the code will be easily maintained.
2 If generalized, peer review outputs will create a quality guide book and best practices
For some developers patterns are intrinsic, while others reinvent the wheel. Standardization and Self-regulation inside the team are required.
3 Peer review is a channel to disseminate knowledge
Let’s end with email memos like: [team] Patterns for Service implementation… And grab the 1-on-1 opportunity to explore a little deeper those sort of concepts.
4 Best off all, an opportunity to exchange ideas and getting to know the ‘Big picture’
Peer reviews on the IT Landscape are more effective when done by senior members of the team. Allowing a broader context to be given.
Nowadays, Peer Reviews don’t require to be formal or even presential.
I had the opportunity to make an assessment on this matter as a Technical Cabinet Consultant for my employer. New tools use a collaborative approach like a social network, and can connect to numerous types of Source Code Management Systems. Different approaches related to the point in time for making the review can be taken (before-commit/after-commit).
Some will always argue that it will increase project effort. But the benefits outweigh the reluctance, in my opinion.
Share your thoughts on this subject!
On the job, people are expected to learn from copy&paste examples. Not asking questions is a sign of ingenuity. If you have luck, a senior member of the team leads the way.
There are countless quality assurance benefits from Peer Reviews, but I’m going to focus on some hidden factors.
Do You Know What You Are Missing?
1 A peer review is an opportunity to evaluate objectively
If a program has zero defects and is delivered on schedule, it doesn’t mean that the best approach was taken or that the code will be easily maintained.
2 If generalized, peer review outputs will create a quality guide book and best practices
For some developers patterns are intrinsic, while others reinvent the wheel. Standardization and Self-regulation inside the team are required.
3 Peer review is a channel to disseminate knowledge
Let’s end with email memos like: [team] Patterns for Service implementation… And grab the 1-on-1 opportunity to explore a little deeper those sort of concepts.
4 Best off all, an opportunity to exchange ideas and getting to know the ‘Big picture’
Peer reviews on the IT Landscape are more effective when done by senior members of the team. Allowing a broader context to be given.
Nowadays, Peer Reviews don’t require to be formal or even presential.
I had the opportunity to make an assessment on this matter as a Technical Cabinet Consultant for my employer. New tools use a collaborative approach like a social network, and can connect to numerous types of Source Code Management Systems. Different approaches related to the point in time for making the review can be taken (before-commit/after-commit).
Some will always argue that it will increase project effort. But the benefits outweigh the reluctance, in my opinion.
Share your thoughts on this subject!