Re: Overtime: the "Bad News" Warning Sign

There are different times of "overtime". In IT, I'd recognize the following types:

Certain work needs to be done outside of office hours. (Installing new memory in a server. Upgrading a database. Recabling the office, etc)
Emergency. (Hardware failure. Software bug causing to lose business. Attack by evil outsiders. System overload.)
Bad planning. (Deadlines)

I don't have a problem doing overwork for the first two cases; that I see as part of the job. The first one is usually planned. If the second one happens too often, something is wrong. The third one I'd be more reluctant. I'm not eager to do overtime if a salesperson makes promises to customers he isn't qualified to make; OTOH, I've worked for employers who do show their appreciation for anyone doing overtime (free food, parties during workhours after the deadline, give time off as compensation without any problems, not complaining if you cannot (or don't want to) do the overtime).

So, do overtime or not? It depends on the reason, the attitude of the employer, and the role you're playing inside the organisation.

Comment on Re: Overtime: the "Bad News" Warning Sign

Replies are listed 'Best First'.
Re^2: Overtime: the "Bad News" Warning Sign by MishaMoose (Scribe) on Dec 29, 2010 at 14:31 UTC
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	[reply]

Replies are listed 'Best First'.

Re^2: Overtime: the "Bad News" Warning Sign
by MishaMoose (Scribe) on Dec 29, 2010 at 14:31 UTC

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

[reply]