Tod1d's Thought Process

Title

Peer Reviews in Software: A Practical Guide - Chapter 2 - Sections 1 & 2

Author

Karl Wiegers

Description

OK, I have already written a nice long description for today's AotW. Unfortunately, I managed to close the browser window I was working in, without saving the blog post. Aaaaaaaaaaargh!!! Rather than run out of my room screaming, I will try and make this short, sweet, and use Notepad2 from now on.

This week's article/essay is neither an article nor an essay. It is the first two sections of the second chapter of Karl Wiegers' book, Peer Reviews in Software. The sections are titled Scratch Each Other's Backs and Reviews and Team Culture. The entire chapter is a bit too long to be an AotW (14 pages). However, the first two sections contain a lot of good information and are a much shorter read (2 pages).

Reading through these sections reminded me that our team needs to be more deliberate about conducting code reviews. We have time set aside for them each week, but, as is often the case, other things tend to get in the way. Code reviews promote idea sharing, and can increase the quality of code.

A big "Thank you!" goes out, to Jeff Atwood for blogging about Karl's work and pointing out that these sample chapters are available.

Favorite Quote

"In a healthy software engineering culture, team members engage their peers to
improve the quality of their work and increase their productivity."

Suggestions?

Do you have a suggestion for the Article of the Week? I would love to hear about it. Please drop me a line and tell me about your favorite online articles/essays. If I like it enough, it may show up in next weeks AotW.