The benefits of code reviews are obvious. It's a deliberate attempt at proofreading code. No writer submits work without it being double-checked. Why should you? A code review can point out potential bugs before QA or the end user does, and verifies that your code is robust and easy to maintain.
Most small shops don't have the resources to conduct code reviews. This is the role I'm hoping to fill. You can see my qualifications
here. Briefly, I've been a developer for over 15 years. I'm certified in .NET 1.1 and 2.0, SQL 2000 and 2005, VB 6, ASP and BizTalk. By most accounts, I'm pretty good at what I do. I've discovered that in addition to writing code, I love reading other people's code and critiquing it. So it follows that participating in code reviews is something I enjoy doing.
Here's how this works: To have me begin a code review, fill out this form here. You'll need to tell me what to check, any specific areas of concern, and special build instructions. I'll email or fax you a non-disclosure agreement stating that I won't tell anyone about your project. We can also negotiate a non-compete. Once that is set, you can begin to upload the source to the site, and any standards/requirements documents that you have. Once I have the source, I'll send you an estimate of time to complete (usually 1-2 days), and a bill.
You'll receive an acknowledgement from me once I've made sure that all the components are present, and that the project builds successfully. I'll then begin reviewing the code compiling a detailed report with my findings, which will be emailed to you.
Since I'm the one who will be reviewing the code, it only makes sense for me to review what I'm proficient in. I can review ASP.NET, WinForms/SmartClient, Web Service, or Mobile projects written in VB/C# .NET 1.1 or 2.0. VB 6 or ASP classic can also be reviewed. I'm also capable of reviewing SQL Server 7.0 - 2005 backend structures as well as Oracle 8i - present. In the near future, I'll add support for BizTalk, WCF and WPF. I just don't have those mastered yet. No COBOL, Powerbuilder, Java, or C++;
The code review is not in anyway a guarantee that your code will be free from bugs after implementing my suggestions. I am not assuming any liability for your code.
This is really a bastardization of the code review process. Code Reviews should be internal, interactive and a learning aid for developers of all levels. I'm offering a pragmatic approach for shops that don't have sufficient resources and want to have some assurance that the code is ok.
I tried to strike a balance between having something affordable for small shops, and worthwhile for me to give up time with my wife and kids.
Basic Package - .30 per line of code, minimum $400
- Build test
- Naming Conventions
- Commenting
- Adherence to your own published coding standard
- Complexity Check
- Error handling/Reporting
- Dead code
- Improvements for Maintainability
Common Package - .40 per line of code, minimum $400
- Is there an easier way to do this?
- Basic Package
- Disposing checks
- Thread safety
- SQL Injection checks
- Input validated
- Overflow conditions
Optimum Package - .50 per line of code, minimum $400
- Common Package
- CAS Configuration
- Support for non-admin users
- Unit Test Code Coverage checking
- Spellcheck English comments and end user text
Line of code are non-whitespace, non commented lines. Use a utility such as Project Line Counter (http://www.wndtabs.com). That is what I use to determine the number of lines.
|