How do you do code review? Do you see it as useful or more of a burden? Please share your views

Code review is done before teh code is launched into the production environment.During code review any changes which are to be done can be implemented prior to deployment into production.

There are some tools available for Code Review ie.PMD , FireBug, Sonar . It is useful to optimize code

Code Review is the part of Development phase of SDLC. Your peer's will review your code and you will review your peer's developed code. Definitely it has got its own importance to find out any possible mistakes in the development stage itself to correct before releasing the code to testing environment, thereby reduces your repeated work and saves time. I feel it is a useful practice in the development stage itself not surely a burden.

Code Review should be a part of your development plan, it is very effective and you could use other techniques to acheive that review, one of them is pair programming.

Also, not all the code should be reviewed, and in order to facilitate that review you should put your own rules, for instance, you can put a rule for any function that shouldn't be more than one visible page.

it's all a matter of what you want to acheive, what scale the quality of your final product should reach, couse for me I might face projects that the delivery matters much more than the quality, and quality could be acheived later after the launch.

Code reviews can be done by a technical leader or a peer. It is useful in either of the scenarios. As a developer, the person may think only in his/her perspective. So brining in a second perspective in most cases makes it easy to do the following:

1. Diminish Code redundancy

2. Bring a functional and system perspective into the code.

3. Bugs not identified in unit testing can be caught

4. Coding standards can be improved.

When the developer is involved with a huge team, it really is advantageous.

When lack of time, I strongly would recommend the developer to verbally outline the code.

Code reviews is very important only if taken seriously as part of development/implementation process. I have conducted code reviews for other people and have had my code reviewed by others as well. I have to say that it is very effective technique in catching programming mistakes and logical errors before the code reaches production. These errors are sometimes very hard to catch by QA. Code review is also necessary to enforce/insure code guidelines and best practices.