Best Practices for Scientific Computing · HackerPapers discussions

Best Practices for Scientific Computing — HN submission

Sun, 09 Nov 2014 22:28:19 GMT

Best Practices for Scientific Computing [pdf]

2 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Best Practices for Scientific Computing — mentioned by dubya

Fri, 10 Oct 2014 17:18:43 GMT

This sounds like a gap in the curriculum that could be filled by grad students. I'm not in CS, but I know that the bioinformatics students have organized a course that covers some basics of the unix command line tools, probably because data conversion is a big part of most projects. There's also "Best practices for scientific computing" (http://arxiv.org/abs/1210.0530) that covers some of the same ground, and physics departments usually have a scientific computing course as well. Also, if it's really a one-off use of something, the department IT person could probably do it for you.

Paper and discussion history. A mention is not an endorsement.

Best Practices for Scientific Computing — HN submission

Mon, 12 Aug 2013 14:21:13 GMT

Best Practices for Scientific Computing

http://arxiv.org/abs/1210.0530

2 points; 1 discussion reply on HN. Paper and source history. A submission is not an endorsement.

Best Practices for Scientific Computing — HN submission

Sat, 02 Mar 2013 15:26:41 GMT

[pdf] Best Practices for Scientiﬁc Computing

3 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Best Practices for Scientific Computing — mentioned by dmlorenzetti

Sat, 29 Dec 2012 16:35:43 GMT

The article is more concerned with "open development" than with "scientific software". Those interested in more specifically science-oriented advice might like the following, which is referenced in the OP: http://arxiv.org/abs/1210.0530. For example, this one mentions version control and testing against data.

Paper and discussion history. A mention is not an endorsement.

Best Practices for Scientific Computing — HN submission

Wed, 28 Nov 2012 14:12:41 GMT

Best Practices for Scientiﬁc Computing

1 point; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Best Practices for Scientific Computing — mentioned by johnx123-up

Tue, 20 Nov 2012 10:14:23 GMT

Recent version is v2 http://arxiv.org/abs/1210.0530v2 Summary: 1. Write programs for people, not computers. 2. Automate repetitive tasks. 3. Use the computer to record history. 4. Make incremental changes. 5. Use version control. 6. Don’t repeat yourself (or others). 7. Plan for mistakes. 8. Optimize software only after it works correctly. 9. Document design and purpose, not mechanics. 10. Conduct code reviews.

Paper and discussion history. A mention is not an endorsement.

Best Practices for Scientific Computing — HN submission

Tue, 20 Nov 2012 09:13:28 GMT

Best Practices for Scientific Computing

20 points; 10 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Best Practices for Scientific Computing — HN submission

Thu, 04 Oct 2012 13:18:57 GMT

Best Practices for Scientific Computing

4 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.