A thing or two about style guides
A style guide should be chosen when working on a solo project or with a team. This keeps the code manageable when you or your peers come back to work on it in the future. It doesn’t matter which style guideline you choose as long as you stick with it. In a sense, writing clean code will also help reduce technical debt. Below is a collection of style guides that I collected over time. Some important rules are repeated in other styles. It’s nice to keep consistency (to a degree) if you are writing in multiple programming languages but ultimately it’s best to do what’s best for each language.
“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.”
Martin Fowler, Refactoring: Improving the Design of Existing Code
Last updated: Feb 8th, 2015.
General
C++
HTML/CSS
- Code Guide by @mdo
- CSS Style Guide
- Google HTML/CSS Style Guide
- HTML(5) Style Guide and Coding Conventions
Java
- Android Code Style
- Code Conventions for the Java Programming Language
- Google Java Style Guide
- Java Programming Style Guide
JavaScript
- Airbnb Javascript StyleGuide
- An AngularJS Style Guide for Closure Users at Google
- GitHub JavaScript style
- Google JavaScript Style Guide
- Node.js Style Guide
Lisp
Objective C
- Apple’s Programming with Objective C Conventions
- GitHub Objective C Style Guide
- Google Objective C Style Guide
- NYTimes Objective-C Style Guide