Comments on: Code Presentation or Inspection? http://www.beilers.com/2009/11/code-presentation-or-inspection/ Crazy Thoughts on Software Development and Life in General Wed, 21 Jul 2010 17:31:27 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Laurinda Wilmer http://www.beilers.com/2009/11/code-presentation-or-inspection/comment-page-1/#comment-2971 Laurinda Wilmer Mon, 07 Dec 2009 02:28:49 +0000 http://www.beilers.com/?p=591#comment-2971 This is a really good read for me, Thanks for posting this informative article. This is a really good read for me, Thanks for posting this informative article.

]]> By: Thomas Budd http://www.beilers.com/2009/11/code-presentation-or-inspection/comment-page-1/#comment-2724 Thomas Budd Mon, 30 Nov 2009 18:47:21 +0000 http://www.beilers.com/?p=591#comment-2724 Hi, gr8 post thanks for posting. Information is useful! Hi, gr8 post thanks for posting. Information is useful!

]]> By: Phil http://www.beilers.com/2009/11/code-presentation-or-inspection/comment-page-1/#comment-2411 Phil Tue, 17 Nov 2009 17:51:24 +0000 http://www.beilers.com/?p=591#comment-2411 I might need to re-check my wording... but I’m actually frustrated by the lack of structure in the code review process, I see too many at the far-right of the spectrum! I rarely see a team follow the "inspection" pattern, most code reviews are too unstructured in my opinion. I also think a tool like Crucible or CodeCollaborator provides the necessary structure and organization to make the review process efficient and valuable. I might need to re-check my wording… but I’m actually frustrated by the lack of structure in the code review process, I see too many at the far-right of the spectrum! I rarely see a team follow the “inspection” pattern, most code reviews are too unstructured in my opinion. I also think a tool like Crucible or CodeCollaborator provides the necessary structure and organization to make the review process efficient and valuable.

]]> By: Gregg Sporar http://www.beilers.com/2009/11/code-presentation-or-inspection/comment-page-1/#comment-2410 Gregg Sporar Tue, 17 Nov 2009 17:03:33 +0000 http://www.beilers.com/?p=591#comment-2410 "This first one really drives me crazy, but unfortunately, this appears to be the way that most teams perform their “code reviews”. " I assume you are referring to the "Inspection" entry at the far-left end of that diagram. If so, I don't agree that a formal inspection approach is the way that "most teams perform" code reviews these days. When I talk to software developers about code review they seldom mention formal inspection methods. I did a presentation on code review just the other day (http://blog.smartbear.com/the_smartbear_blog/2009/11/peer-code-review-an-agile-process.html) and only a few people in the audience had ever done a formal code inspection. These days developers tend to use lighter weight approaches to code review. “This first one really drives me crazy, but unfortunately, this appears to be the way that most teams perform their “code reviews”. ”

I assume you are referring to the “Inspection” entry at the far-left end of that diagram. If so, I don’t agree that a formal inspection approach is the way that “most teams perform” code reviews these days.

When I talk to software developers about code review they seldom mention formal inspection methods. I did a presentation on code review just the other day (http://blog.smartbear.com/the_smartbear_blog/2009/11/peer-code-review-an-agile-process.html) and only a few people in the audience had ever done a formal code inspection.

These days developers tend to use lighter weight approaches to code review.

]]>