in reply to Miscellaneous.pm?
However it does feature in scripts I've written at work, and which may be seen or even adopted by others. In these cases the value of "callum.pm" over "misc.pm" becomes great -- at the very least providing a warning to adopters that it's a personal script.
Obviously things vary according to how public a script is, if it's something that only I will ever use then structure & conventions are essentially just for my benefit and names like sqlstuff.pm, googlestuff.pm even (ugggh!) miscstuff.pm abound; if "real" people are going to see or use the code then most modules will be standard cpan or corporate ones, those that aren't have sensible names, are structured, commented, and maybe even have some error handling ;)
In the middle lie the potential problems; like I suspect many of you, I have a variety of (for wont of a better term) utility scripts that a few others use or copy, and it's helpful in these cases to have a middle ground -- scripts I've thrown together, and that have grown organically (as in -- like mold) over a few years, and which are used by a variety of random techies, who hopefully understand the nature of the code, and who will in general tweak it to suit themselves better anyway.
Obviously this isn't best practice in any sense, but I see it as a reasonable middle ground between "proper" behaviour and the random-script-thrown-together reality.