All geek questions in one place

Tips for improving code review capabilities

How to improve the ability to view code? Any suggestion from personal experience will help.

What are the common mistakes or mistakes made by each of you? How to ensure that problems do not leak out of the code review?

+3
source share
3 answers
  • peers should be familiar with the code base.
  • change should be well limited and not too big
  • the change must be verified before submitting a view request
  • forced execution. no review, no registration.
  • good tools http://www.reviewboard.org/

these are my 2 cents.

+5
source

. , ..
(, Java- CheckStyle), , , ,
+1

.

, :

Each developer must fill out the “verified” field in our tracking system before setting a task for resolution. If the developer believes that a review is not required, he or she should indicate the reason (for example: change the label).

To develop a good code score on a team, you must include everyone. Whenever possible, a review should be carried out by another developer. Therefore, the personal trap is that I am checked every time by the same person.

+1
source

Source: https://habr.com/ru/post/1729524/

More articles:


All Articles