Writing Code for Humans course notes part 2 - Naming

 Naming matters


“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?


"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

The Pragmatic Programmer notes

The cat ate my source code. It’s your responsibility to come up with solutions, not excuses. Sure there’s many things to be taken into account but regardless, JFDI. Broken window theory. Momentum of bad code fucks shit up. Be on top of... Continue →