There is no substitute for a close examination of others’ code before it is released into production. A “code review” is the process of having someone other than the author evaluate a program at various points in the development cycle, prior to placing it into productive use. This article provides a brief introduction to the concept of code reviews — what they are, how they’re conducted, and what benefits you can expect from their use — along with some tips for conducting your own code reviews, including an extensive sample checklist you can use as a template to help you deliver error-free programs on time and within cost constraints.
David F. Jenkins
David F. Jenkins has been involved with IT since 1957, when he started in the business as a punched card machine operator. Dave worked for a Houston bank for nine years before receiving his B.S. in Math from the University of Houston. He then joined IBM, where he worked in various marketing support positions, supporting contractors at the NASA Johnson Space Center. While at IBM, Dave spent a year teaching at New Mexico Highlands University as part of IBM’s Faculty Loan Program. Since leaving IBM, Dave has received a master’s in Management, Computing and Systems from Houston Baptist University, and has finished coursework for a Ph.D. in Management Information Systems at the University of Houston. Since 1996, Dave has been a consultant specializing in ABAP development — his most recent client assignment has been at ChevronTexaco, supporting their installation of SAP IS-Oil Production and Revenue Accounting. Dave is married with four children, and two beautiful grandchildren. He and his wife Joy live in the country 80 miles west of Houston, where they enjoy the wide-open spaces and fresh air, and their dog, cats, fish, and especially their colony of purple martins.
You may contact the author at davidfjenkins@earthlink.net.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.
Premium
Premium