Naming Made Easier
summary
Names stay clear and actionable: prefer descriptive but concise identifiers, group declarations at the top of classes, and keep related classes together in DDD subdomains. Establish a terminology dictionary that maps business terms to code names, use isX / XId indicators for Booleans and identifiers, and append type suffixes like Repository/Service/Entity to classes. Follow modern PHP coding standards (PECR/PSR), avoid obsolete Hungarian prefixes, and run a risk analysis before large renames or refactors.
AI-written summary · about
chapters (11)
- 0:00Naming challenges
- 2:35Why naming is hard
- 6:04Better naming strategies
- 8:12Clear naming rules
- 10:41Grouping declarations
- 12:57Business terminology and DDD
- 15:51Indicators and class naming
- 18:25Naming patterns
- 20:57Function naming grammar
- 22:40Refactoring terminology changes
- 24:28Q&A
