Posted by Maxilect at March 3, 2023, 7:20 p.m.

Yesterday, during the IT gathering, we trained the code review. Of course, we did not invent anything outside of Google's Engineering Practices, but we considered various controversial points:
- how quickly you should start reviewing new code;
- when it is too late to conduct a code review;
- how to change the code review concerning team newcomers and moving from stack to stack;
- where are the stylistic limits of technical remarks;
- is it worth thinking about the fact that comments on a code review can offend;
- what it all has to do with the speed of deployment of the new features.
We've discussed specific tools. There was a discussion about who is responsible for the bugs identified in the code review. By the way, the answer to this question is not as apparent as it seems. Look for an analysis of this discussion in the articles on our Medium blog!