<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Schwarcz, Mati</title>	<link>http://tc.eserver.org/authors/Schwarcz,_Mati</link>
	<description>A bibliography of works by Schwarcz, Mati 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>Schwarcz, Mati</title>
		<link>http://tc.eserver.org/dir/Schwarcz,_Mati</link>
	</image>
	<item>
		<title>The Art of Technical Communication</title>
		<link>http://tc.eserver.org/32133.html</link>
		<guid>http://tc.eserver.org/32133.html</guid>
		<description>Blog on technology and its meaning. Explores different themes and techniques in technical communication and rhetoric.</description>
	</item>
	<item>
		<title>Jabberwock</title>
		<link>http://tc.eserver.org/32134.html</link>
		<guid>http://tc.eserver.org/32134.html</guid>
		<description>Technical editors are constantly required to edit and revise pieces that they don’t fully understand - or even have much information about. That’s part of the game.</description>
	</item>
	<item>
		<title>Learning to Think Critically through Technical Writing</title>
		<link>http://tc.eserver.org/32135.html</link>
		<guid>http://tc.eserver.org/32135.html</guid>
		<description>Although any writing, when taught correctly, will improve a student’s ability to think critically, comparatively speaking, technical writing is a &apos;fast track&apos; to acquiring these skills.</description>
	</item>
	<item>
		<title>Zen and the Art of Technical Writing</title>
		<link>http://tc.eserver.org/32136.html</link>
		<guid>http://tc.eserver.org/32136.html</guid>
		<description>The Technical Writer is normally in a position that requires communicating technical information to a wide audience of developers, implementers, or end users. On the surface of things, writers must satisfy two masters.</description>
	</item>
	<item>
		<title>Jabberwock 2: The Solution</title>
		<link>http://tc.eserver.org/32137.html</link>
		<guid>http://tc.eserver.org/32137.html</guid>
		<description>Technical communication must ultimately serve the reader - there must be something that the writer can do to clarify the information and make reading part of the process that makes the product usable.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Schwarcz,_Mati.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>