|
On Fri, 15 Dec 2006, Mike wrote:
Besides the issues that David mentioned, I think code reviews are best for the newer programmers. You can then show them "a better way" to do things and teach them in the process.
Of course getting a good code review depends on the quality of the programmer doing the review. When I first started I was the new programmer and didn't know much about RPG. The person who reviewed my code was a prolific coder, but not a good architect. I wrote a great deal of code that really wasn't very good but was all reviewed. Later I discovered that I'm a much better architect than he is, but he is better at grinding out code than I am. We have since rewritten a great deal of that code because it was so awful. So the reviewer needs to have his act together.
midrange.com
James Rich
It's not the software that's free; it's you.
- billyskank on Groklaw
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
