|Syntactic Confectionery Delight|
What's in a Name?by schumi (Hermit)
|on May 29, 2002 at 09:32 UTC||Need Help??|
Inspired by this thread I was wondering whether fellow monks follow any conventions when choosing names for programmes and scripts.
I tend to use telling names for programmes and scripts which are operative, like buch.pl for a script which lets people order books; and names which rank from silly to plain non-sense to sometimes outright foul when writing wee test scripts whose life-span is expected to be anything below an hour.
Of course, sometimes these test scripts survive and actually get to be operative themselves, and as long as it's only me handling those scripts that is ok. But no (user|website visitor) should have to see a call for a script named shite.pl, hrmpf.cgi or any such.
And what happens, when someone else has to work with those scripts, say another webmaster, or even a job successor? Names like script1.pl, script2.pl are not exactly helpful to find out what the thing does. But then, sometimes names can be very obvious for the person creating the script, while not at all for others.
How do yous handle this?
There are nights when the wolves are silent and only the moon howls. - George Carlin