QC checklist for 'The Lone Ranger' PERL Programmers (true)
1. Use strict pragmas, set warning flags, write comments
2. CLOSE files as soon as you are done using them. The files will close when your program closes, but you should take control in you scripts.
3. Remove all warnings even if they are not fatal errors do not remove warnings by removing -w.
4. If you are porting files build in DOS or Mac to Unix/Linux, use dos2unix on all files ported in this manner. Using the Unix utility dos2unix, will keep you line endings easily identifiable and parseable in UNIX.
5. Seek code reviews from other coders, even if they do not know Perl. If you can not tell another programmer what each line of your code is doing, then what is each line of your code doing?
If you code with these thoughts in mind, follow these processes, write decent comments, you will find your code is more maintainable, and maybe even beautiful in some places.
"Creative work is not a selfish act or a bid for attention on the part of the actor. It is a gift to the world and every being in it. Don't cheat us of your contribution. Give us what you've got" -- The War of Art: Break Through the Blocks and Win Your Inner Creative Battles by Steven Pressfield.
Programing Articles 
