Code review is a good practice for any developer. And it definitely does not matter how many years of experience you have to participate in code review as a developer or reviewer person.

It helps to keep code clean, well written and stable. In addition, it will force additional knowledge transfer about functionality from more experienced persons.

Here described basic action items for new developers before sending a pull request to review.

Unfortunately more than half of the code reviews have different reasons to be postponed or rejected because of simple mistakes or misunderstandings.

The idea is to describe simple steps to increase code review productivity and as a result focus on more valuable topics to review.

For the first time, let me start from the basics.