Chris's Wiki :: blog/sysadmin/SaveYourTests Commentshttps://utcc.utoronto.ca/~cks/space/blog/sysadmin/SaveYourTests?atomcommentsDWiki2014-07-27T23:36:25ZRecent comments in Chris's Wiki :: blog/sysadmin/SaveYourTests.By Abe on /blog/sysadmin/SaveYourTeststag:CSpace:blog/sysadmin/SaveYourTests:0293801488c87a467d41806cf575c4506b522563Abe<div class="wikitext"><p>Third reason, slightly related to your first reason: No matter how much of a one-off you think something is, you'll find yourself doing the same upgrade/change/test/validation a year or two later.</p>
</div>2014-07-27T23:36:25ZBy Ewen McNeill on /blog/sysadmin/SaveYourTeststag:CSpace:blog/sysadmin/SaveYourTests:9b41801f8b1f8f3a096eff5cf270a51eabf90440Ewen McNeill<div class="wikitext"><p>I'd definitely encourage capturing "how we ran this" information at the top of scripts, in comments. I look at it as "love notes to my future self" -- invaluable in recovering the state of just what I was thinking when I wrote the script and how I used it. </p>
<p>It doesn't even have to be very complicated. For a rough script even just adding "Usage something like:" followed by some cut'n'paste of commands from my shell history at the time can be sufficient. (For something I'm "publishing" I might write it up a bit more formally. But something just saved "in case" it's needed again, the formality can be omitted.)</p>
<p>Ewen</p>
</div>2014-07-27T11:01:34Z