Master the collocations for giving, receiving, requesting, and acknowledging feedback in engineering teams.
0 / 5 completed
1 / 5
The senior engineer took time to ___ specific, actionable feedback after every code review.
Give feedback is the standard professional collocation for providing observations and suggestions to a colleague. 'Tell about' is too informal. 'Deliver away' is redundant. 'Share along' is less precise in a feedback context.
2 / 5
The junior developer found it difficult to ___ criticism without becoming defensive.
Receive criticism is the natural collocation for being on the receiving end of negative feedback. 'Take in around' is informal. 'Accept along' is non-standard. 'Absorb out' is not a valid phrase.
3 / 5
Engineers are encouraged to ___ a review from at least two peers before merging a significant PR.
Request a review is the standard engineering collocation used in GitHub and GitLab workflows. 'Ask for along' is informal. 'Seek out around' is informal and redundant. 'Apply for' implies a formal application, not a peer review.
4 / 5
The developer promised to ___ comments from the code review before the end of the sprint.
Address comments is the standard code review collocation for responding to and resolving reviewer notes. 'Fix away' is informal. 'Respond to all' is slightly less natural. 'Clear out' implies deletion, not resolution.
5 / 5
It is important to ___ suggestions promptly so contributors feel their input is valued.
Acknowledge suggestions is the standard professional collocation for recognising and responding to someone's input. 'Confirm along' and 'note around' are informal. 'Accept out' is not a standard phrase.