It is a good practice to review your code and not wait for the user to complain. Other developers get too much comfortable when testing the software as they think that users make great testers and will eventually tell if something is wrong. This lead to oversight of a crippling bug that affects the business.
Code reviews are extremely important in ensuring the quality of codes delivered. Conduct code reviews as if you are checking the implementation of the code not just abiding some sort of standards like variable naming and layouts. Code reviews keep error rates low.
How do you review codes?
You can do pair programming. In pair programming, one sits on the keyboard and act as the driver. The other one acts as the navigator who guides the driver what to do. Often they switch roles. Having a second pair of eye reduce errors. Peer review also allows junior team members to learn from a senior.
Throwing an all-nighter is also an option. These type of code review can get lengthy and may not sound agile.
What to look when doing code reviews.
You may ask yourself the following questions.
- Can you easily read the code?
- Is there any duplication of code?
- Will the code you are reviewing will have a great impact on other modules if left unoptimized?
- Is there reasonable improvements / good intentions when changing the codes.
Code Review Best Practices
- Promote a positive code review culture. Code reviews can put a strain on interpersonal relationships. It is important for managers to keep it professional.
- Break down code reviews into 60 minutes sessions. Doing the work in one sitting can wreak havoc in the body.
- Do rigorous code reviews to ensure code quality.
- Take your time when reviewing the code. Do not rush to avoid omission of an important line of code.