On 4/8/15 7:55 PM, Marcia K Wilbur wrote: > they have this thing called a Code Review. I like to call it "Show and > tell for programmers". Not a developer here. From what I've seen as I observe others is that "Code Review" is nothing less than good practice. A way to raise juniors to a higher level and a way to keep the seniors from floating away buoyed on their own expertise.
Code reviews should allow an informal environment (but structured) where questions such as "Why'd you do it like that?" isn't frowned upon. I've heard of groups getting together over pizza (paid for by department) to sit in a circle and review changes submitted to change control. In some cases, it reminds people to beef up their comments to explain to others what the heck they were thinking when they decided to do something. It allows for everyone to learn where their weaknesses are and get help and guidance. -- << MCT >> Michael C Tiernan. http://www.linkedin.com/in/mtiernan Non Impediti Ratione Cogatationis Women and cats will do as they please, and men and dogs should relax and get used to the idea. -Robert A. Heinlein _______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
