Why It's Worth Arguing for an Hour About Naming in Code Review
summary
Uses a real-world code review example to show how naming choices reveal development approach and where to draw the line between abstraction and concreteness. Discusses how to pick names that match the original idea's appropriate level of specificity and examines the trend toward increasing abstraction in programming.
AI-written summary · about
chapters (8)
- 0:00Naming in code review
- 5:36Abstraction vs implementation
- 11:35Naming debates take time
- 17:20Abstraction and cognitive load
- 21:27Subjectivity in reviews
- 27:45Business impact of naming
- 32:01Constructive vs toxic discussions
- 35:10Team role in reviews
related talks
01h 17mNaming is Hard: Let's Do Better
26mEven Naming This Talk Is Hard
09mHow patterns in variable names can make code easier to read
30mNaming is Hard!
10mLightning Talks - What's in a name?
01h 02mNaming is Hard: Let's Do Better
48m“Speak” Your Architecture: From Domain Language to Well-Named Components
29mWhat's in a Name: From Variables to Domain-Driven Design