Re^3: what are all the things to be considered to write a effective perl script or module?

The best approach depends on your problem. But for many problems a very good approach is to start with a running program that does nothing like what you need and then through many iterations make it into the program you want. And when I say a running program, there are occasions when I've started with:

#! /usr/bin/perl -w
use strict;

print "Hello, world\n";
[download]

and then evolved it into an entirely unrelated program. (I usually start with a slightly more complex standard template that does things like find the right library path, processes command-line arguments, and has POD stubs.)

This approach may seem weird but it can work quite well. Particularly if you mix it with test driven development.

Comment on Re^3: what are all the things to be considered to write a effective perl script or module? Download Code