At my company, I've experienced receiving a lot slower code reviews than usual. I think this is because I'm on a Platform team but each individual member is very specialized to their focus area. We're encouraged to tag a specific person (and I've been assigned a specific person for my code reviews) as well as the team for broader visibility.
However, I'm often stuck waiting 24-48 hours before receiving anything and always need to ping the person that has been assigned to my reviews. It felt pretty awkward needing to do that all the time so I brought it to my manager. My manager essentially let me know we don't have a good process around code reviews yet and are still figuring it out, and it could be a good opportunity for me to bring a good process to the table. He recommends pinging people in the meantime and to not view it as bothering. I am open to doing that, but still wondering if there is a better way.
I have 2 questions:
This definitely feels like a high-impact opportunity, to change the culture + behavior around code review! I left some thoughts about reviewing code in domains you're unfamiliar with in this answer (and Alex has some great thoughts here)
Finally, could you bring more awareness to the number of code reviews that are done by each person? ("What gets measured get done") Maybe a dashboard which shows who has the highest number of code reviews, and send out an email each week (or ask your manager to) celebrating the top 2-3 people.
Thanks for the answer, Rahul. To get more available reviewers, trying to encourage us to train a bit more in our non-specialized areas is a good idea. On your second, point, I definitely am doing my best there in terms of summary, providing screenshots of the UI changes, making small PRs, etc. To be honest my impression is that people aren't even opening it up which is the big problem. Even though I have someone that my team agreed will be the primary reviewer I am needing to ping him for each review. This is the case even for 5-10 line reviews
I’ve found posting a link to the PR in a forum like Slack can help. If there’s a team channel, posting there can still allow others to read at their leisure. Definitely agree with what Rahul said about providing context.