On Sunday, May 19, 2002, at 12:25 , Timothy Johnson wrote:
> I find that subtleties like Paul's are lost on the majority of users and
> programmers alike out there. I prefer the more direct method of:
[..]
To be honest - herding coders is not a reasonable idea -
and generically should be left to those who do not understand
that it is not an NP complete problem.
#
# USER CONFIGURATION << END >>
# ----------------------------
# (no user serviceable parts beyond here)
They had of course done the important bits from the top down
1. the CVS ID
2. the use section with the obligatory
including the obligatory use vars qw(....);
3. GP programming Info section, including the
reference to their license stand
4. where to find the README - and that there was POD
5. defined the basics of the User Configuration
6. BEGIN {
the variables that were setable for User Configuration
{ yes harry - there are cool times to USE the BEGIN Block }
which is a really good way to make 'publically' usable code
that needs to be uniquely configured for a site...
In like manner a part of the reason that I have been pounding
on the 'and make the POD' - is so that the closest that the
infestation units get to opening your PM is with perldoc -
and since it is self explanatory - and provides the simple
cut and paste interface - they will not go dithering with it,
and in the worst case will sub_class from it - and forget
to call it out as a requirement.
IF you have internally documented and laid out what is inside
your PM/App/Code/WhatEverYouCallThatPerlFooStuffYouDoSoWell -
that explains why this, that or the next arcanea that is not
intuitively obvious to your grandmother - then they will of
course be able to breeze through your code and be able to
maintain it with elegance and elan while you are on your
appropriate compensation time for a job well done.
The problem of course is making sure that the coders in your
clique adopt some common standard. Few of them have any
professional time with actual combat - and hence do not
understand that we do not threaten - and that there will
be no actual warning if it is a professional op - so wagging
things at them that they can not comprehend is at best
emotionally reassuring...
ciao
drieux
---
" No Contract, No Killing, We Are Professionals. "
this is not a threat or a warning, it's a 12-step programme.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
