Comments on: Code Review http://akfpartners.com/techblog/2008/11/17/code-review/ Technical and Leadership Thoughts Sat, 04 Jul 2009 12:46:07 -0600 http://wordpress.org/?v=2.8 hourly 1 By: Abbott, Keeven, Fisher &#038 Fortuna Partners http://akfpartners.com/techblog/2008/11/17/code-review/comment-page-1/#comment-186 Abbott, Keeven, Fisher &#038 Fortuna Partners Tue, 09 Dec 2008 01:02:26 +0000 http://akf-consulting.com/techblog/2008/11/17/code-review/#comment-186 [...] and Severity for bugs are defined, logging definitions must be determined and adhered to.  Code reviews are a way to ensure common usage.  Data being sent to five different files in different formats [...] [...] and Severity for bugs are defined, logging definitions must be determined and adhered to.  Code reviews are a way to ensure common usage.  Data being sent to five different files in different formats [...]

]]> By: Jason Cohen http://akfpartners.com/techblog/2008/11/17/code-review/comment-page-1/#comment-183 Jason Cohen Mon, 01 Dec 2008 19:26:37 +0000 http://akf-consulting.com/techblog/2008/11/17/code-review/#comment-183 Thanks for the kind review! For those of you interested in getting a copy of the book, you can get one free here: http://codereviewbook.com I agree with the conclusion of your post -- any code review is better than nothing. Consider reviewing e.g. just the stable code branch, just during feature-freeze, just the "Top 10 Scariest Files" as voted by the development team, just unit tests, just new hires. Thanks. Thanks for the kind review!

For those of you interested in getting a copy of the book, you can get one free here: http://codereviewbook.com

I agree with the conclusion of your post — any code review is better than nothing. Consider reviewing e.g. just the stable code branch, just during feature-freeze, just the “Top 10 Scariest Files” as voted by the development team, just unit tests, just new hires.

Thanks.

]]>