RE: Tech Writing Curriculum

["Brierley, Sean" <Sean -dot- Brierley -at- Jenzabar -dot- Net>]

Tool use should be taught. Tools are not isolated from all other aspects of
the workplace, tools reflect how technical writers do part of their job day
in and day out and it matters little whether the tool itself caused a
particular workflow or was designed to meet it.

To ignore technical writing tools that are representative of particular
workflows, as I argue Quark, FrameMaker, and Word are, is to teach
soldiering without teaching firearms or carpentry with out teaching how to
use a saw, hammer, and chisel.

Tools are not the only key to technical writing, they are only one part.
However, tools are a necessary part of technical writing. And, yes,
certainly teach the cut-and-paste methods, too.

Sean

> -----Original Message-----
> From:	Andrew Plato [SMTP:intrepid_es -at- yahoo -dot- com]
> --- Glenn Maxey <glenn -dot- maxey -at- voyanttech -dot- com> wrote:
> 
> 
	<snip a whole bunch of stuff about learning the theory of the
profession without using the tools>

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

Collect Royalties, Not Rejection Letters! Tell us your rejection story when you 
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of 
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

  Your monthly sponsorship message here reaches more than
  5000 technical writers, providing 2,500,000+ monthly impressions.
  Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

---
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.