Specialized terminology gives code a consistent vocabulary for the domain it represents. When the same entity is called a client in one place and a visitor in another, readers must translate unnecessarily; consistent names reduce cognitive load and make intent easier to understand. section 2.4
Use domain terminology deliberately when naming:
- Nouns for data, usually singular except for collections. section 2.4
- Question-like names for booleans, such as isUserEligible. section 2.4
- Verb-like names for lambdas that represent actions. section 2.4
- Clear domain names instead of ambiguous identifiers such as x, temp, flag, or data. section 2.4
From generic data to domain intent
A list named users communicates its contents, while selectedUsersForExclusiveGift communicates its purpose and discourages accidental additions or removals. Likewise, a promotional-email method becomes clearer when it consistently uses User, Promotion, birthdayPromotions, and standardPromotions rather than generic temporary names. section 2.4
