7 Comments

Thanks for sharing, Abi.

In some companies I used to have something similar to NudgeBot.

Back in the past I used to beg for reviews, stack branches and PRs to continue my work, which I think it is extremely inefficient.

All of this effort (maintaining a new tool, waiting anyways for people to review, etc.) to not focus on solve the problem: people not working together, in pair for instance.

Expand full comment

Abi, thank you for sharing this insightful overview of Meta's approach to accelerating code reviews at scale. The detailed breakdown of their experiment, from identifying the issue in their DevEx survey to designing and testing the NudgeBot solution, offers a valuable blueprint for Developer Productivity teams.

Expand full comment

Hey Abi! Thanks for the summary, do you know if Meta shared their survey?

Expand full comment

They don’t give the full list of questions from Meta's quarterly developer survey, but they do give the one used for measuring satisfaction with the code review process:

“How satisfied are you with the time it takes to get your diffs reviewed by peers?”

Note: If you’re looking for a full question list for a developer survey, there’s a template for that here: https://getdx.com/template

Expand full comment

For anyone looking to automate nudging for code reviews, are there any open source projects?

Expand full comment

GitHub offers this as a built-in feature following the acquisition of Pull Panda:

https://github.blog/2019-06-17-github-acquires-pull-panda/

Expand full comment

Thanks. We use Gitlab. Will check with them if they have a way of using ML to have more targeted nudge.

Expand full comment