It is very important to make code reviews according to a scenario. The main points are: readibility of the code (without redundants comments or another stuff), reusability (if the code has reusable components, functions ... etc.), testing (need of test cases).
code review, review metrics, reusability, readibility
Reviewing code helps maintain best practices for the code and keep a certain standard across the code base. Elements of the code, including styling, formatting, design patterns, and naming conventions, should be kept consistent.
concret: specific best practice (e.g. use microservice)
Development: Implementation/Code/Build, Development: Testing
Clean Code, https://www.oreilly.com/library/view/clean-code-a/9780136083238/, Robert C. Martin, 2008
In which projects do/did you use this practice?
In every out project, for example https://portfolio.med.muni.cz/
3–5 years of experiences
|1. How do you rate the potential benefit for your projects?||5|
|2. How often are you using that practice?||5|
|3. What is the effort to introduce the practice in your project upfront?||5|
|4. What is the effort to apply the best practice in your project daily basis?||5|
Questions 1, 3 and 4 (1 = Low, 5 = High)
Question 2 (1 = Never, 5 = Always)