Naming Things
summary
Practical rules: use PHP, Composer/PSR‑4 and PHPStorm refactors, write code in English, delete dead code, and prefer clear names over clever ones. Claims include avoid abbreviations and use functions as verbs while using noun phrases for classes. Advice on APIs: keep public add/dispatch methods simple and delegate inside. Gives a worked example: builds a Couch query builder inspired by Doctrine that integrates with the stack and proves the naming patterns useful. Underscore for private vars is discouraged.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:53Why are we naming things
- 5:01We want to create meaning
- 5:46Avoid abbreviations
- 6:37Writing acronyms and uppercase
- 7:17Can you code in your native language
- 9:21Open source code
- 10:49Language
- 11:19Code
- 14:42User Stories
- 15:53Variables
- 20:59Functions
- 26:36Classes
- 26:55Known Phrases
- 27:53Class Names
- 30:43Example
- 31:56Conclusion
- 32:07Thinking ahead
- 33:13Practical things
- 34:15Refactoring
- 34:27Questions
- 39:58Create
