TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
"Excessive" as applied to work hours is essentially a rubber
standard. As we have seen, there are some who think that
anything over 40 is the path to burnout, while others are
just starting to get warmed up at 50. So what it boils down
to is that employees who like to be engaged for long hours
and employers who need employees who like to be engaged
for long hours need to do a better job of finding each other.
> I agree that excessive work hours are harmful to productivity,
> efficiency, quality, and job satisfaction. But I once worked on an
> over-40-hour-a-week team where all of the above were excellent. We
> probably averaged around 45 hours per week; if we had averaged 50 hours,
> *that* would have been excessive. For us. In our situation. At that
> time.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-