Open Data
User login
Username:
*
Password:
*
Request new password
Connections through Taxonomy
|
Get Connected
Close Panel
Open Data
Home
›
coding conventions
coding conventions
Coding Conventions
Submitted by
Kathleen Murtagh
on June 9, 2009 - 11:00pm
in
Public
documentation
FuseCal
Public Display
best practices
coding
coding conventions
git
Use 2 space indents
NO tabs - anywhere
try not to leave trailing whitespace
prefer parentheses around method arguments - ESPECIALLY when the argument list has more than one argument.
Optimize your code for READABILITY first.
always put whitespace between successive elements of a list (e.g. argument list, array)
Version Control with Git
Commit locally very often - you can always rearrange it later.
Agaric
Search
About
Contact
Search
Search this site: