RE: Hardest part of getting started?

["Scott Wilborne" <wilbornes -at- vtls -dot- com>]

While I agree that you should not try to teach writing, I think that it is
important to emphasize the need (and the reasons) to write within your
team's style. Someone new to technical writing may not immediately
understand this concept. Additionally, writers fresh from college might be
inclined to write in a more academic style rather than a technical one. I
would encourage your new employee to read the current documentation to get a
feel for the flow you use. In some cases, it may be helpful to go through an
update of a guide together. This way you could show the writer where to go
for information and other things that can taken for granted such as the use
of headings, bullets, numbers, and indexing practices. Of course, all of
this depends on the experiences of the individual you hire. Some people will
need much more direction than others.



>Like John said, anything above and beyond that actual writing.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

A landmark hotel, one of America's most beautiful cities, and 
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe.  http://ieeepcs.org/2001/

  +++  Miramo -- Database/XML publishing automation.  See us at  +++
  +++  Seybold SFO, Sept. 25-27, in the Adobe Partners Pavilion  +++
  +++ More info: http://www.axialinfo.com  http://www.miramo.com +++

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.