A set of best practices for scientific computing, by Wilson et al (2014).
Scientists spend an increasing amount of time building and using software. However, most scientists are never taught how to do this efficiently. As a result, many are unaware of tools and practices that would allow them to write more reliable and maintainable code with less effort. We describe a set of best practices for scientific software development that have solid foundations in research and experience, and that improve scientists’ productivity and the reliability of their software.
In a nutshell:
- Write programs for people, not computers
- Let the computer do the work
- Make incremental changes
- Don’t repeat yourself (or others)
- Plan for mistakes
- Optimize software only after it works correctly
- Document design and purpose, not mechanics
Read the full recommendations here.