http://www.perlmonks.org?node_id=61369


in reply to Why our company doesn't use Perl :(

I suppose I'd better give a little background on my learning Perl for this reply: I learned, or more correctly I started learning, Perl during a summer internship. I had relatively little recent coding experience except in VB, which was 1994-ish for a school project (A levels for non-'merkins).

I have to say that I genuinely found Perl quite nice to handle: Okay, my first few programs looked like bad BASIC with C syntax but this is to be expected. In time I learned about 'coding standards', although I would call these 'standardised coding standards', mainly because I already used a series of my own devising. Most were in the style of indenting code in loops, map blocks and so forth: The first was, of course, use strict; at all times.

The last rule, when boiled down to its essence, was that they didn't care too much what code standard we used provided that the code was easy to read and maintain and that there was plenty of commenting on the code itself: It must be noted that this kind of mindset, ie. "You've got a brain, use it!", tended to be fairly common. You were expected to just get on with it and use your common sense to know when to shout for help, rather than just ploughing on regardless.

My conclusion is that provided that your code does things in a sensible manner, is secure and is readable and maintainable, imposing extreme or artificial coding standards can waste more time than it saves. I would guess that this depends on the standard of the coders involved.

Just, as they say, my 0.02.

Elgon