Re: CE marking

In article <44D277FD.839C7FBE@xxxxxxxxxxxxx>,
mike.terrell@xxxxxxxxxxxxx says...
Charlie Edmondson wrote:

Michael A. Terrell wrote:




There is a difference in working every possible hour, and pitching in
when there is a real need. I'm sure you wouldn't like to be in the
hospital having surgery and the staff walking out at 5 PM because the
operation took longer than expected, and they didn't want to be late for
tea.


Exactly. Some operations are set up where it is EXPECTED that you will
put in anywhere from 6-20 hours of overtime a week. Sometimes, they
compensate accordingly, but often, it is just assumed that it is part of
your job description. If there is an emergency, I don't mind working
over a while to get things done, but don't consider it a necessary part
of my job everyday. So, if it happens every now and then, no problem.
But, if it happens everyday, you find out things happen like to ER
doctors that have been on duty too long - you make mistakes. If you are
a doctor, people die. If you are an engineer, sometimes the same!

Charlie


Its true for some techs, as well. If they don't do their job right on
some equipment, someone may die. It wasn't engineers who tested and
aligned every "Command destruct receiver" that NASA uses, it was the
production and final test techs at Microdyne, and a lot of sporadic
overtime happened in the 30+ years they were in business. I pulled a
lot of it myself, when there were problems meeting deadlines in special
orders, or for the end of the fiscal year.

Yes, and I've been ordered to work overtime when I had nothing to
do. Management thought it unseemly for us to skate when the people
down the food chain were working all sorts of hours. Development
is like a funnel, it gets tighter at the bottom; design and
verification is at the wider end.

--
Keith
.

Quantcast