A CodeReview Phase always is not that welcome step among developers. Most of us do not want to have faults to be found at us. Is'nt it? But there is a gentle way of indicating faults, so that we can take corrective actions and make our programs more user-friendly (developer-friendly).
Check out the following URL for a friendly CodeReview Checklist that should be helpful, even from during the development stage. The website also gives a 30 day Trial Edition of the CodeReview AddIn, but not many of us can afford it, to be frank.
There are simple Compiler options that can also make us enforce some discipline like Compiling under 'Type 4 Warning Level' and 'Treat Warnings As Errors'. A Warning is just not a warning. The dumb and innocent compiler is really helping us to smell something wrong or out of normal sequence. Hence it would be wiser, to have the warnings corrected too.
Perhaps these are simple and trivial things. But in fact, these simple steps go a long way in making programs robust @Runtime and developer-friendly, in future updates and maintenance.