Prince:Coding Guidelines

Home        Lab Members         Research         Publications         Internal         Mass Spec         Contact        

The most important consideration is to correctly solve the problem at hand. However, your code will become useful beyond the original task as you follow these guidelines:

• Keep it DRY (Don't Repeat Yourself)
• Write specs for your code (spec-more, bacon, and rspec are good for this)
• Code should be self documenting
• Code should also be documented, to be clear
  • YARDoc is the preferred tool, then TomDoc
• Follow semantic versioning practices
• Follow Ruby Best Practices