And why are you limiting your thinking that way? Do you take it for granted that Perl works perfectly. Are you under some illusion that you actually have a clue how Perl works?

Did you know that /California/ will match faster against a long string than /Cali/? Do you have a clue why?

Perl 5.6.0 has a bug. The following prints 10 instead of 210. Do you have a clue what could possibly cause this? Do you have any idea what is going on inside of Perl here? 

my $x = 10;
$x = '2' . $x;
print $x + 0;

[download]
Right now Damian Conway and I have been trying to puzzle out a bug in the development release of Perl. It appears to be a bug in Perl. What, we have no idea. What are you going to do with a bug which really is not in your script? I say that advisably. When I throw in: 
require Data::Dumper;
print Dumper(\%call_info);

[download]
inside a function and it not only does not print but jumps out of several layers of functions, something is seriously wrong with Perl.

There is nothing, zero, zilch, nada special about programming scripts and modules that suggests that due diligence there is any more important than at other levels in the tool-chain. The only difference is that you think you understand what is happening there so you can go into your faux-paranoia and refuse to use code which was probably written by people who are far more competent than you.

And even if you are a better programmer, they probably know more about the problem domain that they are working with than you do. Besides which fresh code is by nature more prone to bugs than tested code.

In short, I absolutely agree with clemburg. You either are a hopeless wreck or you use things that you don't understand all of the time, and by claiming to refuse to do so you are demonstrating your ignorance. If you refuse to use that you have not personally audited merely because it is at a level you can try to figure out, then you are being ridiculous.

By all means audit the code, figure out how it works. Find bugs. Fix and report them. Don't use stuff once you have good reason to think it is buggy. But don't pull this he-programmer silliness, you aren't good enough. Perhaps if your name was Theo de Raadt I might respect it. But you are not.

In reply to Re (tilly) 3: Modules Vs. Manual Coding by tilly
in thread Modules Vs. Manual Coding by Chady

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.