Use a version control system diligently, and strive for small, focused changes with meaningful and descriptive commit messages.
Strive for simple, well-commented, self-documenting code with meaningful variable names
Adopt or develop community documentation standards to describe your computational models (e.g., ODD)
Adopt a consistent, self-describing directory structure for your code, data, documentation, and results
Provide clear example test cases, with well documented sample inputs and expected outputs
Use relative paths instead of absolute paths when referring to input or output data files
Structure your code with clarity, reuse and future comprehension in mind and adopt your modeling language and platform’s conventions and idioms for writing easily comprehensible, as concise as possible, well-encapsulated code
you'd like to know more information about what data we collect and why, please see