Here is a checklist everyone should use when doing code reviews:

  • As a reviewer do you understand the changes?
  • Do we have sufficient details about changes being done on Jira or Merge Request?
  • If change is very complex, do we need KT session with team?
  • What are the changes in configurations?
  • Have we done changes in configuration files for all environments?
  • Is Unit Test Coverage dropped?
  • Is code formatting correct?
  • Is code quality correct?
  • Is there any Hardcoding?
  • Have we written a big function which can be divided into small function for easy understanding of code?
  • Have we created/updated Unit Test Cases?
  • Have we created/updated Integration Test Cases?
  • Is there any impact on performance, if we have added major calculations?
  • Is performance impacted, if we are making new API calls?
  • Are we logging important info, warning and error messages?
  • Are we collecting right metrices?
  • Have we notified different stake holders for upcoming changes?

Rakesh Kalra

Hello, I am Rakesh Kalra. I have more than 15 years of experience working on IT projects, where I have worked on varied complexity of projects and at different levels of roles. I have tried starting my own startups, 3 of those though none of it were successful but gained so much knowledge about business, customers, and the digital world. I love to travel, spend time with my family, and read self-development books.