in reply to Avoiding silly programming mistakes

Um, always use strictures (use strict; use warnings; - see The strictures, according to Seuss). :-D

Try whittling problem code down to a small sample suitable for posting to PerlMonks - you almost never have to post the actual code though.

Use a good syntax checking editor. Heed all warnings. Write test suites and run coverage tests.

Avoid writing code (use other peoples modules - CPAN).

Think about edge cases and test for them.


Perl reduces RSI - it saves typing
  • Comment on Re: Avoiding silly programming mistakes

Replies are listed 'Best First'.
A reply falls below the community's threshold of quality. You may see it by logging in.