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.
Subject:What is Hard Work? From:"Anthony Markatos" <tonymar -at- hotmail -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Wed, 29 Sep 1999 11:25:34 PDT
Question for all: What is hard work?
Some Technical Writers say "Forget defined processes -- I get things done by
Einstein said, "Never confuse motion with action". It is difficult for me
to believe that Einstein was never involved in a software
Typical development/documentation project: Coders banging away at their CRT
hour-after-hour (when they are not reading programming books). Technical
writers often following suit. Management loves it; after all, everybody is
working through lunch and putting in plenty of OT.
Working real hard - right? Wrong! This is hacking: a very
obsessive/compulsive, one-sided, activity that always results in poor
Hard work is doing tough analysis work and then switching mental gears to
effectively communicate with other developers and the end users.
Note: As a very wise manager once told me, 'switching mental gears' is the
main reason we resist defined processes. Defined processes prompt us to 'to
what needs to be done'. And for most people 'switching gears' to 'do what
needs to be done' is just 'to much'.