Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site isrnix.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!inuxc!iubugs!isrnix!pugsly
From: pugsly@isrnix.UUCP (David A. Roth)
Newsgroups: net.jobs,net.college
Subject: Re: Overtime pay for professionals???
Message-ID: <642@isrnix.UUCP>
Date: Sat, 14-Dec-85 21:24:29 EST
Article-I.D.: isrnix.642
Posted: Sat Dec 14 21:24:29 1985
Date-Received: Mon, 16-Dec-85 04:59:26 EST
References: <1418@rayssd.UUCP> <957@mako.UUCP> <452@mot.UUCP> <73@calma.UUCP> <794@sfmag.UUCP>, <217@pluto.UUCP>Re: Overtime pay for professSat, 14-Dec-85 21:24:29 EST
Organization: Indianapolis, Indiana
Lines: 21
Xref: watmath net.jobs:1664 net.college:959

In most of the programming positions I worked in overtime was not required but
assumed. Most people worked overtime simply because they wanted too.
If you are interested in something and like working on it and if no one expects
you to work overtime and you do it on your own, fine.
 
  
BUT, those lame reasons managers calling you not a "team player" or "lack of commitment" is hog wash.
Most overtime is caused by mis-management and lack of planning. These
so-called emergencies usually happen because of the above.
Taking it out on the people you manage is not only not right it will come back to haunt you
in the form of turnover and upset employes.
  
The suggestion made to of course try and avoid all this by talking about
all this during the interview and again with your manager.
  
The company you work for doesn't give there goods away..and nether should you!
  
David A. Roth
...decvax!pur-ee!isrnix!pugsly
...ihnp4!isrnix!pugsly
Indianapolis,IN