<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Plamondon, Robert</title>	<link>http://tc.eserver.org/authors/Plamondon,_Robert</link>
	<description>A bibliography of works by Plamondon, Robert in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Plamondon, Robert</title>
		<link>http://tc.eserver.org/dir/Plamondon,_Robert</link>
	</image>
	<item>
		<title>Technical Writing&apos;s Big Secret</title>
		<link>http://tc.eserver.org/31939.html</link>
		<guid>http://tc.eserver.org/31939.html</guid>
		<description>The big secret in technical writing is that most of the harder documents aren&apos;t written by the technical writers at all. In fact, many &quot;technical writers&quot; never do any writing at all. Instead, the drafts are written by engineers or marketers. The technical writers perform editorial functions and provide publications services -- copy-editing, layout, review management, and so on.</description>
	</item>
	<item>
		<title>Technical Writing&apos;s Big Secret</title>
		<link>http://tc.eserver.org/22350.html</link>
		<guid>http://tc.eserver.org/22350.html</guid>
		<description>Technical writing tells the reader how to use a product. If the product can be used successfully by a technically unsophisticated reader, the manual can be written by an unsophisticated writer. It helps if the writer has enough background to understand the product designers&apos; technical jargon, but this isn&apos;t absolutely necessary.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Plamondon,_Robert.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>