Comments on: Agile Development At Latitude – A Progress Report http://blog.geocortex.com/2008/04/13/agile-development-at-latitude-a-progress-report/ Web-based GIS, software development & various other topics of interest to us. Sun, 05 Sep 2010 07:34:36 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Kevin Rintoul http://blog.geocortex.com/2008/04/13/agile-development-at-latitude-a-progress-report/comment-page-1/#comment-5567 Kevin Rintoul Tue, 27 May 2008 05:02:34 +0000 /blogs/geocortex/archive/2008/04/13/agile-development-at-latitude-a-progress-report.aspx#comment-5567 Thanks for your comments. We use FxCop for automating a portion of our code reviews and it seems to work pretty well. We get the most benefit from using it, provided we use it from the beginning. It can be daunting task to apply the tools retroactively. One of the things we're doing on the Optimizer project is to mandate that our code runs cleanly through FxCop before a check-in. This seems to have had a very beneficial impact on our code quality. Thanks for your comments. We use FxCop for automating a portion of our code reviews and it seems to work pretty well. We get the most benefit from using it, provided we use it from the beginning. It can be daunting task to apply the tools retroactively. One of the things we’re doing on the Optimizer project is to mandate that our code runs cleanly through FxCop before a check-in. This seems to have had a very beneficial impact on our code quality.

]]> By: Mark Stock http://blog.geocortex.com/2008/04/13/agile-development-at-latitude-a-progress-report/comment-page-1/#comment-5566 Mark Stock Wed, 14 May 2008 00:32:18 +0000 /blogs/geocortex/archive/2008/04/13/agile-development-at-latitude-a-progress-report.aspx#comment-5566 I am constantly evaluating software and source code. It sounds like you are on the right track. What has helped take some of the drudgery out of the process is using Code Review software. This is automated software that checks source code and highlights the most obvious problems. I like to make automated code review a stage in the build process. You state: "it is really difficult to review a feature consisting of several thousand lines of code scattered over a large number of files." I like your honesty. I think that this may be what the code review is about, honesty. I don't know of any code review software as smart as you. You are at least aware of the problem. And, I see this particular type of problem more often than not. This in itself is the review. I am being honest about the mess I've coded. And, sometimes there is an advantage to coding a big bloated mess in that I can initially deliver software faster. After a review, we can decide to refactor, rewrite, or do nothing. Code reviews are great, and it's also important to move onward quickly. I am constantly evaluating software and source code. It sounds like you are on the right track. What has helped take some of the drudgery out of the process is using Code Review software. This is automated software that checks source code and highlights the most obvious problems. I like to make automated code review a stage in the build process.

You state: “it is really difficult to review a feature consisting of several thousand lines of code scattered over a large number of files.” I like your honesty. I think that this may be what the code review is about, honesty. I don’t know of any code review software as smart as you. You are at least aware of the problem. And, I see this particular type of problem more often than not. This in itself is the review. I am being honest about the mess I’ve coded. And, sometimes there is an advantage to coding a big bloated mess in that I can initially deliver software faster. After a review, we can decide to refactor, rewrite, or do nothing.

Code reviews are great, and it’s also important to move onward quickly.

]]>