Naming Things (without notes)

There's an old joke that goes, “The two hardest things in programming are cache invalidation, naming things, and off-by-one errors.” In this talk, we'll discuss the subtle art of naming things – a practice we do every day but rarely talk about.

Transcript

2. @aupajo .co.nz
3. @aupajo NAMING
 THINGS
4. What is code?
5. What is good code?
6. Why is naming things important?
7. Why is naming things hard?
8. VARIABLES
31. METHODS
36. CLASSES
46. CONVENTIONS
53. NAMING ERGONOMICS
61. What is it you do?
62. Programs must be written for people to read, and only incidentally for machines to execute. “ Harold Abelson Structure and Interpretation of Computer Programs
63. @aupajo Slides twitter.com/aupajo
65. The ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. Making it easy to read makes it easier to write. Robert C. Martin “Uncle Bob”
66. The ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. Making it easy to read makes it easier to write. Robert C. Martin “Uncle Bob”
67. The ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. Making it easy to read makes it easier to write. Robert C. Martin “Uncle Bob”
68. A parable about stones
69. On Exactitude To my mind exactitude means three things above all: (1) a well-defined and well-calculated plan for the work in question; (2) an evocation of clear, incisive, memorable images; (3) a language as precise as possible both in choice of words and in expression of the subtleties of thought and imagination. - Italo Calvino