Naming as a Process (NaaP)

Refactor with Less Risk

  • Trust the names in your team’s code.
  • Spend less time coming up with names.
  • Waste less time hunting for experts on code you don’t understand.
  • Less code to read and understand for each story.

01 — Make an Honest Name

State exactly what you know, and not what you interpret or assume.

02 — Use Obvious Nonsense

Delay naming until we have more information.

03 — Add a Fact

Gather and record information instead of trying to understand.

04 — Refine a Question

Eliminate rabbit holes that force you to read and verify.