Is a carefully managed IT lifecycle always good for the business? I once had a junior front office support role (my first Perl job in fact) where I sat in a team of three Perl/Sybase/unix people. One day a trader came along (at 11am) and said "I need this Reuters page published by 3pm". The team leader asked, "what is the impact if it isn't ready on time?". "Oh, we'll lose about $100 million" came the reply.

The team-leader said to me: "we can't allow the business to put that kind of pressure on our IT methodologies - leave this with me and don;t do anything." -- and wandered off.

Thanks to the power of Perl and my experience with language processing software in general, I had a working database to Reuters-page translation programme ready in time. Meanwhile the team-leader had gone and got permission from the global head of IT to say no and let the trader lose the $100 million. The value of the IT department's work for a year can't possibly have amounted to that much! Needless to say I lost that position soon after because I didn't fit in (and wouldn't have wanted to!).

__________________________________________________________________________________

^M Free your mind!

In reply to Re: IT decisions are driven by business needs by Moron
in thread IT decisions are driven by business needs 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.