HN Explorer

Ask HN: How do you get developers to review pull requests more frequently?

4 points by Bahamut ↗ HN
One problem that I have encountered frequently as a developer is people being reluctant to review pull requests with any regularity, often leaving pull requests to hang until their work is done, then dumping a lot of changes requested.

Has anyone else encountered this problem, and how did they solve it? Currently I devote a lot of time reviewing pull requests to keep development moving faster through shorter feedback cycles, but as a lead developer, I wonder if this is an effective use of my time. I feel like I am depriving opportunities for my team to learn & grow through greater code exposure, but at the same time, I also understand that most developers are not great at context switching & reviewing code changes ends up being a context switch away from regular product development.

1 comment

[ 77.3 ms ] story [ 1013 ms ] thread
akjetma
The CTO at my company recently decreed PR reviews to be the number one priority during the day. Seems to have helped make clear the importance of reviewing things. I think when it's explicitly and clearly mandated from a superior, it makes it easier to justify the cost of the context switch and I also think it's a good idea at an organizational level to prioritize this.