Rather than overtime #1 should be covered by proper work schedules. These things are usually known in advance and schedules of the individuals involved can generally be adjusted to cover it without overtime

#2 shoudl be coverd by some sort of rotating on call schedule that covers at least the triage of these issues. Actual over tiem should be kept to a minimum by not expecting a regular 8 hour work day following the completion of an emgergency all nighter. And yes I have wokred jobs where this was the attitude. "Why are you going home at 11 am for the day!??" "Maybe becuase I have been here working with the vendor to fix the problem for 20 straight hours?"

Of course we are not helped by those in our profession who sit on their hands while things go to hell .. so that they can pull all nighters to 'save the day' before some important event and be heroes. I have seen way too much of this (especially with government contractors) those who create emergencies by negligence and shine when they put in massive overtime to save the demo. They get promoted for their "dedication", where those who do their work diligently abnd correctly are unknown to the senior managment and remain mostly invisible.

Misha/Michael - Russian student, grognard, bemused observer of humanity and self professed programmer with delusions of relevance

In reply to Re^2: Overtime: the "Bad News" Warning Sign by MishaMoose
in thread Overtime: the "Bad News" Warning Sign by locked_user sundialsvc4

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.