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
- What did OpenAI’s Habitat team change?
- Does the reported 12× read improvement mean another team should copy the design?
- Does the Python Typing Survey measure all Python developers?
- Do Python type hints enforce types at runtime?
- What is interactive refactoring in gopls?
- Is interactive refactoring already part of the official LSP standard?
- What does Meta mean by human-on-the-loop software engineering?
- Does Meta's Forum project prove that AI can replace a software team?
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.