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.

 
1
Kudos
 
1
Kudos

Now read this

Notes from The Developer’s Code book

Start from the most interesting task first. We’re allowed to do that as developers, a more realistic timeline can be established once we have practical experience in doing. Only then will we know how much time is accurately required to... Continue →