If you're calling me paranoid

I'd place your knowledge of the possibility that "Yes, sure, if other team members ... create snapshots by some other method" under the same category as "actual experience, or documentation", so no, you're not paranoid.

Though I'd have to suggest that it might be better to ensure, (mandate; by providing a library to generate the tags), that they do not use some other method, than to look for work-arounds for the possibility that they do. If they do not include a timestamp, how are you going to "decide which objects are old enough to delete"?

Using defensive programming to handle the possibility in production -- and paying the inevitable costs for doing so, which on a platform where you are paying directly for cpu usage directly affects your bottom line -- is a poor substitute for weeding out such errors(*), during pre-production testing.

(*if you mandate the tag format, non-compliance becomes an error.)

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^3: 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.