What’s in a name? that which we call a rose
By any other word would smell as sweet;

William Shakespeare

Coding, Then and Now

The 16K ZX Spectrum

Strategies around Naming

Naming is difficult, so do it right

Naming is Hard Work

Add Value At The Point of Use

Name Types and Variables after their Role NOT their Type

Name Methods After their Side Effects

Side Effects

Protocol or Interface Naming

Be Explicit

Respect the Idiom of the Programming Language

Differing Language Idioms

Clarity is Important not Brevity

The Standard is the Standard is the Standard

Apply the Naming Standard Consistently without Exception

Applying a Standard Consistently Aids Refactoring and Assimilation

Defining a Naming Standard

If there is no Naming Standard, Define One

Suggested Contents in a Naming Standard

Final Thoughts

Apple Bigot of note. Dylan, LISP, Smalltalk and Swift fan. Passionate about software architecture, coding and design patterns. Science fiction fan and Trekkie.