Best Practices of Code Review

  1. Project and filename should be self explanatory like PaymentService
  2. Remove unwanted import/using packages statement (use specific lib, don't use * until unless it require)
  3. Sort all the import/using statement properly
  4. Don't ignore warning in your project (Address it all and remove), force zero warning before production check in
  5. Code consistency, reusability and readability
  6. Do extra care for NULL all the times and put check to handle NULLpointException handler
  7. Remove unwanted dead/un-used code like variable not being used in application
  8. Naming convention
  9. Write proper exception handling (try, catch & finally)
  10. Properly use access specifier based on architecture (public, protected & private)
  11. Self documenting code/comments in your code

You can use lot of readymade tools available like FindBug, SonarCube etc.

Comments

Popular posts from this blog

PUTTY - The server's host key is not cached in the registry cache

OIM-12c Installation - FMW - SOA - IDM

SAML & OAuth 2.0