Would that it could be that way, but it isn't. *sigh*

However, I do get to make decisions about how it's being worked the 'long way'. And if they come back in a week or so and say "we want to make this change", I get to tell them, "Well, I could do that, but you see, I had to do this to accomodate the last thing you changed. This will push the timeframe back (2*x)2", where "x" is the time it will acutally take me to do it, and the expression is the "estimated" cost to the timeline in double "x" in the next increment in time. Therefore, if it would take me 2 hours, I would "estimate" the impact on the work schedule at 4 days.

Feel free to use this formula anywhere useful. Yes, it's a "ShareWare Contractor Estimator". :)

In reply to Re: Re: Parsing XML into a Hash by mcogan1966
in thread Parsing XML into a Hash by mcogan1966

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.