Unfortunately, the people who pay us do not always view things rationally; in particular, they tend to be quite happy to rubber-stamp existing ongoing expenses, and very reluctant to authorise new expenditure, even when the new expenditure could reduce the ongoing expenses.

Or, to put it bluntly: in my experience, most PHBs would rather you wasted two weeks optimising your code, than spend $8,000 on a server upgrade.

Why? I don't know for sure. The optimist in me says it's because my salary has been budgeted for, and there's no room left in the budget for hardware. The cynic in me says that it's because they don't feel they have any control over schedules (everyone knows IT projects always run late!), but they do have control over the purse-strings, so they control what they can. Or maybe it's because they think that we're being lazy, asking for faster hardware instead of doing our jobs properly and writing fast code, and they don't want to reward laziness?

Really, heaven only knows. But it's a fact of life for some of us... and that means we do have to worry about CPU cycles, because even if they're irrelevant in dragonchild's Utopia of limitless upgrades, the real world is not so generous.

In reply to Re: CPU cycles DO NOT MATTER! by Porculus
in thread CPU cycles DO NOT MATTER! by dragonchild

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.