I tend to err more often on the side of applying some extra error checking and logging when it isn't needed,

This is going to sound supercilious, and there is nothing I can do about it.

Don't err .. find out.

The source of the OPs data is most likely this API. And the source of that API is whatever filesystem + metadata that underlies the Amazon EBS filesystem. Which AFAIK means, that unless you are party to some inside information, your (the OPs) only choice is to trust the results that API returns are uncorrupted; because you (he) simply do not have enough information to determine otherwise.

So in this case, erring on the side of caution isn't "a sensible precaution", nor "being proactive"; nor "good methodology"; it is a complete waste of either your employer's or client's time, resource and money. And yours. Performing a test, because it is easy to do, despite the fact that you know it will only detect some minuscule percentage of the possible failures, all 3-sigma outliers to boot, serves only to slow things down for no statistically likely benefit.

It is supplementing a belt made of kevlar, with braces made of overcooked spaghetti. Or betting an accumulator on two successive lotteries.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^5: HoA create from array using map, more efficient? by BrowserUk
in thread HoA create from array using map, more efficient? by hsinclai

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.