This response generates two thoughts for me: 1) version control can be used as a notebook, if you use a good directory structure and excellent commit messages. In fact I use it that way for myself (granted, I don't run a biolab, but most of the analysis he describes would fit what I do, e.g. always move forward, are very simple, the changes are obvious, etc) -- big plus: I don't have to remember yet-another-password and learn yet-another-tool, in fact I don't use dropbox at all.
2) testing -- this is particularly important to me. In fact I think that as soon as one has learned ifs, fors and functions, before trying to do anything else, one must learn testing. Cheers, Dav On Thu, Mar 3, 2016 at 7:25 PM, Greg Wilson <[email protected]> wrote: > Arjun Raj has done another blog post about reproducibility, version control, > appropriate tooling, and the like at > http://rajlaboratory.blogspot.ca/2016/03/from-over-reproducibility-to.html - > lots in it to think about. > > - Greg > > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
