There are only two hard things in Computer Science: cache invalidation and naming things -- Phil Karlton
Naming convention is a set of rules for choosing the character sequence to be used for identifiers which denote variables, types, functions, and other entities in source code and documentation.
Reasons for using a naming convention (as opposed to allowing programmers to choose any character sequence) include the following:
- To reduce the effort needed to read and understand source code;
- To enable code reviews to focus on more important issues than arguing over syntax and naming standards.
- To enable code quality review tools to focus their reporting mainly on significant issues other than syntax and style preferences.
- C# Coding Standards and Naming Conventions
- Git Comment Convention
- JavaScript Name and Coding Conventions
- Powershell name convention
- R style guide and name convention
- SQL Server Name Convention and T-SQL Programming Style
- NET Naming Guidelines
- Framework Design Guidelines
- Google style guides for open source projects
- Google R Style Guide
- Google Python Style Guide
- Google C++ Style Guide
- Google HTML/CSS Style Guide
- Google Java Style Guide
- Google JavaScript Style Guide
- Google JSON Style Guide
- Google Common Lisp Style Guide
- Google Objective-C Style Guide
- Google Shell Style Guide
- Google Vimscript Guide
- Google XML Document Format Style Guide
- An AngularJS Style Guide for Closure Users at Google
- MSDN Powershell Style Guide
- MSDN Approved Verbs for Windows PowerShellCommands
- The PowerShell Best Practices and Style Guide
- PostgreSQL naming conventions
- SEI CERT Coding Standards
- SQL Server Documentation
- SQLite Documentation
- PostgreSQL Manual
- Oracle DB documentation
- MySQL documentation
- C# Language (C# Programming Guide)
- JavaScript
- Sensible CSS Guidelines
- R Language (R Language Definition)
- Transact-SQL (T-SQL Reference)
- Procedural Language/PostGres Structured Query Language (PL/pgSQL Manual)
- Python PEP