Which guideline is violated if different names are used for the same concept in an API?

Which guideline is violated if different names are used for the same concept in an API?

• A. G1 Beware of lots of same-type values
• B. G2 Choose unambiguous names for related things
• C. G3 Beware of false consistency
• D. G4 Focus on user experience

Answer: (B)

The guideline that is violated when different names are used for the same concept in an API is about choosing unambiguous names for related things. Consistency in naming is crucial in API design because it helps users to easily understand and interact with the API. When the same concept is represented by different names, it introduces ambiguity and can lead to confusion among developers who are trying to use the API. They may struggle to determine whether these names refer to the same entity or if they have different meanings, which can negatively impact their experience and increase the potential for errors. By ensuring that names are unambiguous and consistent across the API, you help foster clearer communication and intuitive interaction with the system, making it easier for users to write code, debug issues, and understand the API's functionality. This principle emphasizes the importance of nomenclature that clearly reflects the underlying concepts they represent, thus improving overall usability and reducing the cognitive load on users.

The guideline that is violated when different names are used for the same concept in an API is about choosing unambiguous names for related things. Consistency in naming is crucial in API design because it helps users to easily understand and interact with the API. When the same concept is represented by different names, it introduces ambiguity and can lead to confusion among developers who are trying to use the API. They may struggle to determine whether these names refer to the same entity or if they have different meanings, which can negatively impact their experience and increase the potential for errors.

By ensuring that names are unambiguous and consistent across the API, you help foster clearer communication and intuitive interaction with the system, making it easier for users to write code, debug issues, and understand the API's functionality. This principle emphasizes the importance of nomenclature that clearly reflects the underlying concepts they represent, thus improving overall usability and reducing the cognitive load on users.