On Thu, Mar 10, 2016 at 4:36 AM, Steven Haddock <[email protected]> wrote:
> Exactly! thus a ~/scripts folder in your PATH and under version control… > This is really the most real-world solution. On Thu, Mar 10, 2016 at 9:51 AM, Ivan Gonzalez <[email protected]> wrote: > Regarding how to organize code, this paper [1] recommends to have a > "scripts" directory under version control at the root level of your project. > I greatly favor the approach Ivan brought up [1]: keeping scripts with each project rather than adding them to my PATH. Unless my script is both stable and useful enough to be worth semantic versioning [2], I don't want to risk screwing up a bunch of other projects when I fix a bug affecting just one. This *can* result in redundant code across projects, but that's usually a good sign that I should put the work in to clean up and package those scripts. [1] http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1000424 [2] http://semver.org/ -Byron
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
