Naming/Names

• Name for the purpose, not implementation.
  • Example: activeTeamMembers instead of filteredUsers.
• Stay consistent.
• Context is important.
  • While in context of a class we can use shorter names, example Note.id is clear that its the id of the note. No need for redundant Note.nodeId naming. Outside of this context make sure its named namedId and better yet has strong typing for the type of values it holds using techniques like Branded Types in TypeScript, Value Classes in Kotlin
• Variable names to be VALID for Entire Duration of Function

---

Children

1. Variable names to be VALID for Entire Duration of Function