Comments on: Managing, Reviewing, and RESTing http://third-bit.com/blog/archives/1126.html Data is ones and zeroes | Software is ones and zeroes and hard work. Tue, 22 May 2012 16:23:22 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: David Wolever http://third-bit.com/blog/archives/1126.html#comment-1263 David Wolever Thu, 06 Sep 2007 17:43:48 +0000 http://pyre.third-bit.com/blog/archives/1126.html#comment-1263 "I don’t know if I’ll be able to persuade my students to start critiquing their teammates’ code, but having read this book, I’m certainly going to try." Sounds like a good DrProject plugin :) “I don’t know if I’ll be able to persuade my students to start critiquing their teammates’ code, but having read this book, I’m certainly going to try.”

Sounds like a good DrProject plugin :)

]]> By: David Sitsky http://third-bit.com/blog/archives/1126.html#comment-1262 David Sitsky Mon, 03 Sep 2007 01:45:53 +0000 http://pyre.third-bit.com/blog/archives/1126.html#comment-1262 There are a number of free code reviewing systems around these days. I used to work at Cisco many years ago where code reviewing was done with email clients, and they were just starting to introduce to our section full-on code inspection meetings, which involved print-outs and meetings. While the found defect count rates were very high, so was the overheads in performing these meetings. When I moved to a fast-paced startup afterwards, I wrote a perl CGI script to do code reviews online, so that the process was somewhat more casual, but it allowed people to browse changes and make comments in a more structured manner. Importantly, the overheads in performing these reviews was kept low. This is when I created Codestriker, located at http://codestriker.sf.net, and the project has been growing slowly since then. Its not the world's prettiest program, and is probably showing its age now, but I still find casual inspections before check-in to be a valuable part of the software development process. There are a number of free code reviewing systems around these days.

I used to work at Cisco many years ago where code reviewing was done with email clients, and they were just starting to introduce to our section full-on code inspection meetings, which involved print-outs and meetings. While the found defect count rates were very high, so was the overheads in performing these meetings.

When I moved to a fast-paced startup afterwards, I wrote a perl CGI script to do code reviews online, so that the process was somewhat more casual, but it allowed people to browse changes and make comments in a more structured manner. Importantly, the overheads in performing these reviews was kept low. This is when I created Codestriker, located at http://codestriker.sf.net, and the project has been growing slowly since then.

Its not the world’s prettiest program, and is probably showing its age now, but I still find casual inspections before check-in to be a valuable part of the software development process.

]]> By: Greg Wilson http://third-bit.com/blog/archives/1126.html#comment-1261 Greg Wilson Sun, 02 Sep 2007 22:11:18 +0000 http://pyre.third-bit.com/blog/archives/1126.html#comment-1261 Yes, there's discussion of the psychology involved, and of management practices --- they cover all the bases (as far as I can tell). Yes, there’s discussion of the psychology involved, and of management practices — they cover all the bases (as far as I can tell).

]]> By: Guillaume Theoret http://third-bit.com/blog/archives/1126.html#comment-1260 Guillaume Theoret Sun, 02 Sep 2007 17:49:00 +0000 http://pyre.third-bit.com/blog/archives/1126.html#comment-1260 Do they talk about the emotional impact of peer code review? Many shops function according to the idea of "code ownership" (which I think is bad) and this would make critiquing someone's code critiquing the person himself. Do they talk about the emotional impact of peer code review? Many shops function according to the idea of “code ownership” (which I think is bad) and this would make critiquing someone’s code critiquing the person himself.

]]>