How does a consistent naming convention affect onboarding of new developers?

• A. Speeds onboarding due to predictable structure.
• B. Increases onboarding time due to rigid naming.
• C. Has no impact on onboarding.
• D. Forces developers to memorize every name.

Answer: (B)

A naming convention that is consistent creates a predictable map of the codebase. When file names, classes, functions, and directories clearly reflect their purpose and relationship, a new developer can infer what something does and where to find related pieces without friending through guesswork. This reduces the time and mental effort required to understand how the system is organized, so onboarding goes more smoothly and quickly.

The idea that consistency would slow onboarding because it’s rigid isn’t aligned with how people learn code. A well-chosen, stable naming system lowers cognitive load, improves searchability, and helps you recognize patterns across the project. It also means you don’t have to memorize arbitrary names; meaningful names convey intent and context, making it easier to navigate and understand new components.

It’s also not true that naming has no impact or that you must memorize every name. Clear conventions guide newcomers, helping them predict where to look for related functionality and what a component does based on its name, which accelerates learning and reduces confusion. In practice, teams couple naming standards with onboarding docs and examples to reinforce correct usage and expectations.