Practise the standard verbs for giving code review feedback with a constructive tone.
0 / 5 completed
1 / 5
Fill in: 'We ___ every comment around the code, not the person who wrote it, since 'this function' reads very differently to an author than 'you' does.'
We 'phrase a comment' — the standard, simple collocation for choosing the specific wording of review feedback. The other options are less idiomatic here.
2 / 5
Fill in: 'Writing terse, unexplained comments during review can ___ a junior author assuming the criticism is harsher than the reviewer actually intended.'
We say a terse comment will 'leave' an author assuming harsher intent — the standard, natural collocation for the resulting misread. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a suggestion as a question where genuinely possible, since 'why not use a map here?' invites discussion in a way a flat instruction doesn't.'
We 'frame a suggestion' — the standard, simple collocation for choosing how a piece of feedback is presented. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ nitpicks clearly as optional in the comment itself, so an author can tell instantly which feedback blocks merging and which is just a preference.'
We 'label a nitpick' — the standard, simple collocation for marking the severity of a review comment explicitly. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a reviewer's time explicitly in the pull request description, since a thorough review is genuine effort, not an obligation owed for free.'
We 'thank a reviewer' — the standard, simple collocation for acknowledging the effort behind a code review. The other options aren't idiomatic here.