atw: Re: University Research Project - How to avoid working in a void?
- From: Craig Hadden <CraigH@xxxxxxxxxxxxxxxxxxx>
- To: "'austechwriter@xxxxxxxxxxxxx'" <austechwriter@xxxxxxxxxxxxx>
- Date: Tue, 21 Oct 2003 09:46:48 +1000
Maray (Sherwood) wrote:
> Sometimes ...you are not seeing or doing what you are writing about...
> How do [you] overcome this ...?
Maray, my take on this would be that you can write some parts of the
documentation (e.g. conceptual topics like "What is a widget?") without
access to what you're writing about. But you might not be able to write
procedures accurately, particularly if your audience has little knowledge
(and therefore the steps need to be very detailed).
So, you could structure your time to write and/or check the detailed
procedures while you have access, and write other content when you don't.
Hope that helps,
Craig
**************************************************
To post a message to austechwriter, send the message to
austechwriter@xxxxxxxxxxxxxx
To subscribe to austechwriter, send a message to
austechwriter-request@xxxxxxxxxxxxx with "subscribe" in the Subject field.
To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with
"unsubscribe" in the Subject field.
To search the austechwriter archives, go to
www.freelists.org/archives/austechwriter
To contact the list administrator, send a message to
austechwriter-admins@xxxxxxxxxxxxx
**************************************************
Other related posts:
