Even Naming This Talk Is Hard
summary
Argues that naming is the core problem not the topic and gives concrete failures and fixes: builds a mental to‑do app as a running example, finds naming collisions on GitHub and runs into invites for events, sees real code where containers vs dumpsters collides with Redux terminology and Docker, documents how organizations replace blacklist/whitelist with allow lists and block lists, shows tooling that helps (searches, linters, style enforcers) and offers practical heuristics for when to refactor names.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:31Hello my name is RUTHIE Bunruthless
- 4:17WHY IS IT HARD TO NAME SOFTWARE?
- 17:22WHY DO BAD NAMES PERSIST?
- 17:51THE PROBLEMS CAUSED BY THIS NAME DON'T AFFECT ME. THEREFORE THEY DON'T EXIST.
- 19:42I DON'T BELIEVE THAT CHANGING THIS NAME WILL MOVE THE NEEDLE ON WHAT WE CARE ABOUT.
- 20:20WHAT MAKES A NAME GOOD OR BAD?
- 23:04HOW CAN WE NAME SOFTWARE BETTER?
- 24:52NO JUDGMENT ZONE
related talks
26mEven Naming This Talk Is Hard
01h 17mNaming is Hard: Let's Do Better
36mWhy It's Worth Arguing for an Hour About Naming in Code Review
29mWhat's in a Name: From Variables to Domain-Driven Design
10mLightning Talks - What's in a name?
30mNaming is Hard!
20mName Things Once
09mHow patterns in variable names can make code easier to read