Types of Code Reveiws

• Pair programming.
  • Two developers share a workstation. They work together to build and review  code in real time, talking about design choices and how to put them into action. details as they happen. 
  • Pair programming encourages close teamwork and quick feedback, which improves the quality of the code, and sharing what you know.
    • Pair programming or rapid code review can help when you're trying to solve hard business problems that need close working together and quick feedback for developers. 
    • Working together can come up with ideas for solutions, talk about edge cases, and make sure that all situations are handled correctly in the code. taken care of in the code. 
    • Pair programming works best when both programmers are at around the same level of skill, which lets them work at a steady pace and work together to solve problems. It encourages learning from each other and motivates people, which leads to better code quality and more work getting done.
• Ad Hoc Reviews
  • AD hoc reviews are code reviews that happen when they are needed and are not planned. 
  • Developers can ask their coworkers for feedback or check each other's code on their own without following a set plan. 
  • Ad hoc evaluations aren't as formal, but they can still give you useful information and help you find problems early. during the course of development.
• Over-the-shoulder Revew
  • Over the shoulder reviews involve one developer physically sitting with another and reviewing their code.
    The reviewer provides feedback and suggestions in real time as they examine the code together.
    Over the shoulder reviews are beneficial for immediate feedback and knowledge transfer, but may not be practical for remote or distributed teams.
• Tool Assistance
  • Tool-assisted reviews use unique code review tools or platforms to make the review process easier. 
  • These tools have capabilities like "code diffing" to show any differences right away and "inline commenting." issue tracking and workflow management to make the review process faster and better for working together.
• Formal Inspection
  • Formal inspections, also known as peer reviews or walkthroughs, are all types of systematic and thorough code reviews processes that are done according to set rules and checklists.
  • Participants usually include developers, testers, and other interested parties who carefully look at the code for bugs, following rules, and meeting requirements. 
  • Formal inspections take longer, but they can be very helpful for finding complicated problems and making sure the code is of excellent quality. 

• Synchronous Code Review
  • The coder writes the code on their own and then reviews it immediately, with the reviewer discussing and improving the code together.
  • It's helpful when the reviewer doesn't know what the work goals are or when there are a lot of code changes to make are expected.
    • Synchronous code reviews are appropriate when the reviewer lacks understanding of the changes made by the coder.
    • In such cases, immediate collaboration and explanation can help clarify the code and ensure that feedback is relevant and accurate.
    • If extensive code improvements are expected due to the coders lack of experience or familiarity with the task.
    • Synchronous reviews allow for real time discussion and iteration on the code.
    • This can accelerate the review process and ensures that improvements are made efficiently.
• ASynchronous Code Review
  • The coder completes the code and makes it available for review. The reviewer then reviews the code at their own pace, providing commands and suggestions asynchronously.
    This type is beneficial when there is no direct dependency between the code and the reviewer, and allows for flexibility in scheduling.
    Asynchronous code review can be done with assistance of different tools for code review.
    • Asynchronous code reviews are suitable as a default option for professional development teams due to their flexibility and efficiency.
    • This prevent the need for force context switching, where developers are interrupted from their current tasks to participate in a review session. 
    • Asynchronous reviews are effective for most common use cases, where developers can review code independently and provide feedback asynchronously. 
    • This type is ideal for teams with diverse schedules and distributed members.
• Code Review Once in a while
  • This method involves periodic code review sessions conducted by the entire team, where one developer presents a piece of code they have been working on, and the team collectively reviews and discusses it.
    While not a permanent option, it can be useful for teams new to code reviews.
     

There are pros and cons to each sort of code review, therefore you need to choose which one to utilise based on based on things like the size of the team, the difficulty of the project, the way development is done, and the culture of the organisation.

Asynchronous code reviews are the recommended default option for professional development teams due to their flexibility and efficiency. Synchronous reviews and Pair programming can be utilized when necessary, such as when immediate collaboration is required or for solving complex business problems.