When of the following is BEST described as "a benefit of using a standard naming convention"?

A standard naming convention's primary benefit is enhancing readability and understandability for developers and operators. Consistent names for variables, functions, files, or infrastructure resources make the system's purpose and structure self-evident. This clarity reduces cognitive load, simplifies maintenance, and accelerates debugging and onboarding of new team members. While other benefits like sortability may arise from specific naming patterns, readability is the most fundamental and universal advantage that underpins overall code and system quality.

A. Sortability is a benefit of specific naming schemes (e.g., using date prefixes), but it is not the universal primary benefit of all standard naming conventions.
B. Abstraction is a design principle for hiding complexity; while good naming supports it, the convention's main goal is clarity, not abstraction itself.
C. Indexation, or making items easy to find, is a positive outcome of good naming, but it is a secondary benefit derived from the primary goal of readability.

1. Martin, R. C. (2008). Clean Code: A Handbook of Agile Software Craftsmanship. Prentice Hall. Chapter 2, "Meaningful Names," extensively discusses how the primary purpose of naming is to reveal intent and improve readability.

2. MIT OpenCourseWare. (2016). 6.031: Software Construction. Lecture 2: "Designing for Readability." This course material emphasizes that a key goal of coding style, including naming conventions, is to make code readable for other humans. (ocw.mit.edu/courses/6-031-software-construction-spring-2016/).

3. McConnell, S. (2004). Code Complete (2nd ed.). Microsoft Press. Chapter 11, "The Power of Variable Names," states that a good variable name's primary goal is to provide clarity and understanding, which is synonymous with readability.