In
<8124033304576715.wa.elardus.engelbrechtsita.co...@listserv.ua.edu>,
on 09/26/2013
at 01:19 AM, Elardus Engelbrecht <[email protected]>
said:
>Indeed. In a mature Data Centre, such overtime may or may not be
>frowned on, but you know there are exceptions and of course
>changes needed to be done after hours.
In my experience, super long shifts are expected for emergencies,
either real or simulated. In that situation, sleep deprivation will
impair your judgement, which is why management should step in and
order you to rest even if you think that you can keep going. Providing
three hots and a cut can reduce the length of an outage. Oh, and good
managers will order everybody out who is not contributing to the
solution[1]; they can wait until the system is back up before doing
their post mortem.
Changes can be scheduled to avoid excessive overtime. Typically I've
seen a 4 hour window on weekdays and a longer window on weekends, but
I've never been at a shop that expected a 24-hour or longer shift for
routine maintenance.
>I don't have any confirmed proof, but apparently the Japanese people
>are FORCED to have leave to take a break every year.
I really dislike the combination of forced leave and unpaid overtime.
There's also the question of who decides when the leave is to be
taken.
[1] I've seen it done, and it really speeds up problem resolution
when you don't have to keep explaining what happened, what
you're doing about it and when the system will be back up.
"Are we there yet?"
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
