Brent Clark wrote:
Hi all
Howdy,
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
I am very fortunate to work in an environment where all the devs
subscribe to Damian Conway's "Perl best Practices".
Still there are times when compromises must be made and much of that
depends on all the folks involved. Unfortunately the things you can't
control (The tosser's ego for instance) have nothing to do with what is
best for the project.
Moron higher ups that like to do it one way because that is what they
know (you knwo the "I've been doing this since you were a lad" guy) and
don't want to appear wrong, stupid, or are just lazy (or on the rare
occasion, because it is the best way ;p)
The best policy is communication, openmindedness, and compromise.
Many times small proof of concept code to compare the benefits and
downfalls of a certain idea are good (even if it means we now see *our*
negative sides...)
Then if he signs the check just smile and nod adn do it his way :)
HTH :)
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
