Practise the standard verbs for keeping code comments accurate and useful.
0 / 5 completed
1 / 5
Fill in: 'We ___ a comment explaining why a workaround exists, not what the next line already makes obvious, so the reasoning survives long after the author has moved on.'
We 'add a comment' — the standard, simple collocation for documenting reasoning inline. The other options are less idiomatic here.
2 / 5
Fill in: 'Leaving a comment unupdated after the code beneath it changes can ___ a future reader trusting an explanation that no longer matches what actually runs.'
We say a stale comment will 'leave' a reader misled — the standard, natural collocation for the resulting confusion. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every comment during review just as closely as the code itself, since a misleading explanation can cause more damage than no explanation at all.'
We 'review a comment' — the standard, simple collocation for scrutinising inline documentation alongside the logic it describes. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a redundant comment that just restates the line below it, since it adds noise a reader has to filter out rather than genuine understanding.'
We 'delete a comment' — the standard, simple collocation for removing documentation that no longer earns its place. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a TODO comment with an owner and a ticket number, rather than leaving a vague note that quietly turns into permanent, unowned technical debt.'
We 'tag a comment' — the standard, simple collocation for attaching ownership and tracking to a deferred task. The other options are less idiomatic here.