A great article, glad to see some details on the subject.
One thing I've always wondered, since I've only worked at 1 company that used code reviews, is how people structure their code reviews. Can you share on how it works for you guys, in terms of who reviews who's code? Is there one senior dude that always reviews? Or is it just a regular task in the development workflow, so that anyone can just pick up the task and do it?
Well this is a topic that bothers me personally – how to create an environment that encourages every team member to participate in code review on equal status. I mentioned in the article that I find it beneficiary that everyone acts both as a reviewer and reviewee. Right now, until the process and the organization matures enough, we often proactively ask more junior guys to take part as reviewers just by assigning the review as a task for them. But I hope it will once become a habit and the part of a normal workflow like it happened with CI or unit testing for us.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A great article, glad to see some details on the subject.
One thing I've always wondered, since I've only worked at 1 company that used code reviews, is how people structure their code reviews. Can you share on how it works for you guys, in terms of who reviews who's code? Is there one senior dude that always reviews? Or is it just a regular task in the development workflow, so that anyone can just pick up the task and do it?
Well this is a topic that bothers me personally – how to create an environment that encourages every team member to participate in code review on equal status. I mentioned in the article that I find it beneficiary that everyone acts both as a reviewer and reviewee. Right now, until the process and the organization matures enough, we often proactively ask more junior guys to take part as reviewers just by assigning the review as a task for them. But I hope it will once become a habit and the part of a normal workflow like it happened with CI or unit testing for us.