princepawn,

With all due respect, I have personally found it helpful to take the extra time to be self-effacing in online circles.

As a scientist, I'm sure you can appreciate the importance of proper data collection techniques. Is it not wise and proper to ensure the collection process doesn't taint (pun intended) the experiments, the results, and the conclusions being observed?

Besides, what's wrong with stepping back and mentally testing your conclusions and hypotheses against the observed results? This is, in many ways, basic programming.

To provide a perl example from my own experience, I had a dickens of a time getting sub's to work when I first tackled them. It finally worked when I prepended an ampersand to the name of the subroutine. I (erroneously) assumed that perl requires ampersands when invoking custom procedures, much the same way it requires symbols in front of variables.

Since then, I've learned that the rules are more subtle and more flexible and I've modified my mental understanding to allow for that.

Remember Occam's Razor: When faced with more than one equally viable explanation for a problem, more often than not, the simplest solution is the right one. (Poorly paraphrased, I know, but you get the idea.)

Just a thought...

In reply to RE: RE: RE: RE: (Ovid - question your posting strategy) by footpad
in thread What Data::Dumper dumps is not necessarily what is there by princepawn

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.