How to start the path of the code reviewer?

Question

IT education

What skills should a code reviewer have to be interesting to potential employers? I want to start my journey in this area, but I don’t understand where to start and what to focus on.

Answer 1

Awesome question, after the first wtf - confuses - I don't know what to answer. Okay:
2-3 years of commercial development, knowledge of Java, patterns, algorithms, frameworks, and all third-party tools that can be used in the code that you will review. Well, business processes, perhaps.
PS If trolling is not the worst question, I smiled.

Answer 2

You open https://codereview.stackexchange.com or https://ru.stackoverflow.com and review.

Answer 3

You need to have developer skills.
It is also extremely necessary to have a certain amount of logic and non-laziness in order to read what the review code is and not ask stupid questions.

Answer 4

Here you can immediately see the "effective manager".
Already there was not such, but in something similar question Quality of work of the regular programmer. How to evaluate?
This is the eternal managerial desire to "cut corners", and this eternal managerial question "How to learn to objectively evaluate the quality of a programmer's work without becoming a programmer yourself?". And the answer is no.
Of course, there are all sorts of metrics: the time spent on the task, the number of bugs found in the task, etc.
But they still do not give a complete picture.
If you want to review - become a programmer, grow at least to the middle, then the review skill will come by itself. And if there are any magic "code review for managers" courses, then I'm even afraid to imagine the consequences when graduates of these courses begin to review the code of combat programmers, especially middles and seniors.