Typically, it's been my experience that the guy signing the paycheck, or the
one in charge of the project, is the guy calling the shots. If he wants to
utilize a coding technique that is neither secure nor understandable, then
he will eventually reap the benefits of his narrow-mindedness. If you have
done your part in explaining the reasons for using modules, taint mode, etc
and he refuses to (or cannot) understand the wisdom, then do it his way.
Of course, there are three other alternatives -
1) Do it your way and send out some resumes.
2) Go over his head to his boss, explain your logic and send out some
resumes.
3) Just send out some resumes.
Good info Ron :) A couple years ago, where i was at, I couldn't do #2
(since my boss was the ego that thought he was all powerful) so I did #3
and have never been happier!!
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
