|Software Carpentry's Best Practices|
|Written by Mike James|
|Wednesday, 08 January 2014|
Software Carpentry's aim is to make scientists better equipped to work with software just as if it was any other lab apparatus. Now we have its take on "Best Practices" and it is a lesson to us all scientist or not.
Software Carpentry teaches scientists to work with software in a more logical and organized way than is typical, In the old days lab equipment was mostly hardware and it was an important component of any experiment. It was put on show and scrutinized by other scientists. Not so with most of the software and even the data that is involved in most modern experiments. Scientists tend to take a casual approach to programming because it is so much easier than hardware. Of course well all know that it is only easier when you first start. As you slowly tangle yourself up in logical knots it gets harder and harder to work with. As a result lots of scientists tend to hide their code way and the same with raw data.
The point is that that the scenario just outlined not only applies to scientists but to just about anyone using or creating software in anything other than completely trivial ways.
In a recently published paper Software Carpentry outlines what it considers to be "best practice" and it is a document that has a relevance well beyond the strictly scientific.
It presents 24 specific things scientists, or programmers in general, can do to get more done in less time with less pain:
For a more detailed explanation of each one see the paper which is free to download.
To be informed about new articles on I Programmer, install the I Programmer Toolbar, subscribe to the RSS feed, follow us on, Twitter, Facebook, Google+ or Linkedin, or sign up for our weekly newsletter.
or email your comment to: firstname.lastname@example.org
|Last Updated ( Wednesday, 08 January 2014 )|