Skip to main content
7 events
when toggle format what by license comment
Feb 22, 2018 at 12:41 comment added user296862 Good point Doc. I hastily edited point 3 to be less critical of itself.
Feb 22, 2018 at 12:41 history edited user296862 CC BY-SA 3.0
added 64 characters in body
Feb 22, 2018 at 12:40 comment added Doc Brown This is a fine answer (+1). However, option 3 is not necessarily so bad as it described here, and is not necessarily only a solution in case of "political issues". It is a solution for anything for which it is not quite clear if version control will be ever required (like supplemental documents, drafts and sometimes scripts). Of course, when scripts which belong to a specific project which is already in version control, the scripts should be also there.
Feb 22, 2018 at 12:38 comment added user296862 I agree. OP said that if the scripts had to be high quality, developers would be reluctant to write/commit them. That's a red flag to me. I did not say the CLI scripts had to have high code quality -- mine personally fluctuate. However, if you are committing these to VCS, you do have to write at least readable scripts that other developers can actually maintain if you get hit by a bus. Tools for developers can more acceptably be of lower quality, but that doesn't mean they should be.
Feb 22, 2018 at 12:36 comment added Mael I don't think that writing "poor quality" throwaway scripts means you have poor work ethic. I routinely write quick-n-dirty scripts to automate work (even if I could just bang the xargs/sed/etc. one-liner directly in the shell) and commit them to the repo, but I would never push production code written in the same manner. They are two different (very different) things.
Feb 22, 2018 at 12:30 review First posts
Feb 22, 2018 at 12:36
Feb 22, 2018 at 12:28 history answered user296862 CC BY-SA 3.0