> -----Original Message----- > From: Brent Clark [mailto:[EMAIL PROTECTED] > Sent: Thursday, 20 April, 2006 09:39 > To: Perl FAq > Subject: Coding Styles > > > Hi all > > > I seem to be having a few run ins with the "Project Leader", in > terms of my coding style. > > Im very much for modularizing my work - hence the OO concept. > That is creating packages using return in my subroutine etc (Oh > and using strict) > But the ex Cobol Project Leader does not want .pm. Varibables has > to be of a certain naming type convention like the value from a > html text box has to begin > with an i (e.g, $iabc), and strict does not need to be used, hell > neither is #!/usr/bin/perl -T. > > Obviously im frustrated, and either im totally missing the point > and dumb or im working with a real tosser. > > So my question is, for those out there working a dev environment, > would anyone care to share if my way of thinking is wrong etc. > Or anything for that matter > > Kind Regards > Brent Clark > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > <http://learn.perl.org/> <http://learn.perl.org/first-response> >
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. Welcome to the wonderful world of working for others. =) Peace - Ron -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
