<html><body bgcolor="#FFFFFF"><div><br></div><div><br>On Aug 29, 2011, at 12:14, Jeff Frontz <<a href="mailto:jeff.frontz@gmail.com">jeff.frontz@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Often the most important resource is sitting in front of the keyboard,</span><br><span>trying to debug something in the middle of the night when production</span><br><span>machines are collapsing all around. If it takes half an hour to</span><br><span>understand a clever hack before you can get the system back up, was it</span><br><span>really worth saving that minute or two of CPU time over the course of</span><br><span>a year?</span><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#0023A3"><br></font></font></div></blockquote><div><br></div>Exactly. In the real world, you might be trying to decipher someone else's script at 0300 during an outage - or them yours.<div><br></div><div>I try (but don't always succeed) to write and document my scripts for myself, for others who might have to use them later, and to set a good example for anyone using my scripts as a guide for learning & writing their own.</div><div><br></div><div>-rj<br><div><br></div><div><br></div><div><br></div><br><blockquote type="cite"><div><span></span><br><span>Jeff</span><br><span></span><br><span>_______________________________________________</span><br><span>colug-432 mailing list</span><br><span><a href="mailto:colug-432@colug.net">colug-432@colug.net</a></span><br><span><a href="http://lists.colug.net/mailman/listinfo/colug-432">http://lists.colug.net/mailman/listinfo/colug-432</a></span><br></div></blockquote></div></body></html>