Should you mix naming conventions in one codebase?
No. Mixing camelCase and snake_case in the same codebase increases cognitive load and causes real bugs, such as mismatched keys between APIs and databases. Pick the convention native to your language, document it, and enforce it automatically with tools like ESLint or Prettier.
Answered in
Programming Naming Conventions Explained: camelCase, PascalCase, snake_case & MoreLearn the difference between camelCase, PascalCase, snake_case, kebab-case and UPPER_SNAKE_CASE — which languages use which, and how to name things cleanly.
Read the full analysisOther questions this article answers
More development best practices questions
- Why is a large-scale test framework migration usually so slow to do by hand?
- Why did retry loops with error feedback outperform carefully engineered prompts?
- When does a migration pipeline need rich prompt context instead of just retries?
- How do you migrate the last 3% of files that automation can't fully finish?
- Does this approach only work for test framework migrations?
- What is Project Polaris and how does it relate to GitHub Copilot?
- What architecture does Project Polaris use?
- How does Project Polaris perform compared to GPT-4 Turbo on coding benchmarks?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.