Naming Convention Consistency Language Collocations
Practise the standard verbs for keeping naming consistent across a codebase.
0 / 5 completed
1 / 5
Fill in: 'We ___ a single naming convention across the codebase for boolean flags, so a reader isn't left guessing whether 'isActive' or 'activeFlag' is the pattern in use.'
We 'enforce a convention' — the standard, established collocation for requiring consistent naming across a codebase. The other options aren't the recognised term here.
2 / 5
Fill in: 'Letting every team pick its own naming style for the same concept can ___ a simple search for a term returning three different names for the same field.'
We say inconsistent naming will 'leave' a search fragmented — the standard, natural collocation for the resulting confusion. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a new variable name against the existing glossary before introducing it, so 'user' and 'account' don't end up meaning subtly different things in different files.'
We 'check a name' — the standard, simple collocation for verifying terminology consistency before adding new code. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ an inconsistent name during code review rather than letting it merge, since renaming later touches far more files than catching it now.'
We 'flag a name' — the standard, simple collocation for raising a naming issue during review. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the naming guide periodically against real code, since a rule nobody actually follows anymore is worse than having no documented convention at all.'
We 'audit a guide' — the standard, simple collocation for periodically reviewing a standard against actual practice. The other options are less idiomatic here.