On 6/5/06, Anthony Ettinger <[EMAIL PROTECTED]> wrote:
On 6/5/06, Terrence Brannon <[EMAIL PROTECTED]> wrote:
> But really, the last company that I was at (Friendfinder.com) forbade
> the use of map or grep. And violation of the coding standards was
> grounds for immediate termination. I was miserable at this company.
What was the reasoning behind no grep or map?
They felt that it could become confusing when multiple conditions were
and'ed and or'ed together. They said "use programming constructs which
are more in line with most programming languages" -- so you had to
write for loops and push values onto arrays
What I fear is having people review my code who aren't savvy enough to
use warnings or strict in their Perl code, not to mention readability.
Yeah, when you have a company of more than 20 developers, none of whom
are connected to the Perl community. All of whom probably had not read
or even heard of "Perl Best Practices", "Higher Order Perl". None of
whom attend Perl conferences. And most of whom are senior to you, you
feel like you are screaming at a brick wall. They hadn't heard of
several modules like Params::Validate, List::Utils, etc, etc.
I've basically resolved that I can handle a six-month contract
anywhere doing anything even if I hate it. But will only take a perm
role if I really feel I can be permanent there. But with the divorce
rate higher than 70%, should anyone be seeking the perfect matrimony?
