Writing Code for Humans course notes part 2 - Naming

Naming matters #

Classes #

“Is the class doing too much?

  1. It should be a noun
  2. It should be specific
  3. It should have a single responsibility
  4. Does having an instance of that class name make sense?

Methods #

"What does this logic attempt to accomplish?”

Just have them own a self explanatory description

Rubber Ducking #

That eureka moment by talking to yourself.

Rhetorical questions out loud provoke the subconscious.


Now read this

Pluralsight - Clean Code: Writing Code for Humans course notes part 1

Resources # Code Complete 2 Clean Code The Pragmatic Programmer Conventions # Comparisons vs Snippets Verbalize Code. Literal reading code Three Principles for Clean Code 1) Right tool for the job: Less logic code required Learn multiple... Continue →