note
greenFox
<p>Ditto everything [graff] [id://500884|said]. The point about looking at old code is one of the best ways I have learnt, when I have had to go back and maintain code which I wrote and found I couldn't understand chunks of it I knew I had work to do. I am probably overly verbose in my coding now but I know it will be clear when I come back to it in 1 year or 3. A lecturer in one of the few comp sci classes I took said that "a program is a letter from one programmer to another that a computer just happens to be able to understand", I think that is a good way to approach all your programs, like it is a letter to another programmer who you know nothing about.
</p>
<p>
Other resources which you might find useful are [dominus]'s Program Repair Shop and Red Flags [http://www.perl.com/pub/a/2000/04/raceinfo.html|I], [http://www.perl.com/pub/a/2000/06/commify.html|II] and [http://www.perl.com/pub/a/2000/11/repair3.html|III]. I haven't had a chance to read it yet but judging by the [http://www.oreilly.com/catalog/perlbp/chapter/|sample chapter] you will also want [isbn://0596001738|Perl Best Practices] by [TheDamian].
</p>
<div class="pmsig"><div class="pmsig-56270">
<p>--<br /><font size=-1><a href="http://www.insubstantial.com.au">Murray Barton</a><br /><i>Do not seek to follow in the footsteps of the wise. Seek what they sought. -Basho </i></font></p>
</div></div>
500881
500881