<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Hamilton, Richard</title>	<link>http://tc.eserver.org/authors/Hamilton,_Richard</link>
	<description>A bibliography of works by Hamilton, Richard 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>Hamilton, Richard</title>
		<link>http://tc.eserver.org/dir/Hamilton,_Richard</link>
	</image>
	<item>
		<title>Does DITA Make You Dumb?</title>
		<link>http://tc.eserver.org/35375.html</link>
		<guid>http://tc.eserver.org/35375.html</guid>
		<description>There are at least two broad categories of technology that managers often confuse. The first is technology that replaces a particular skill. For example, the cash register at a McDonalds has technology that relieves cashiers from doing math, so they can hire people who are not skilled in math. The second is technology that allows a skilled practitioner to be more productive. For example, the computer makes it possible to write and edit text much more easily than a typewriter, but it won’t make a bad writer better.</description>
	</item>
	<item>
		<title>Content Reuse: Is It Harmful?</title>
		<link>http://tc.eserver.org/32820.html</link>
		<guid>http://tc.eserver.org/32820.html</guid>
		<description>For a number of years it has been a matter of faith that the more content a technical documentation team reuses, the more efficient they are presumed to be. But, are you really more efficient? Let’s take a deeper look.</description>
	</item>
	<item>
		<title>Seven Tips for Living with Technology</title>
		<link>http://tc.eserver.org/31757.html</link>
		<guid>http://tc.eserver.org/31757.html</guid>
		<description>After living through more than a few technology acquisitions, variously as perpetrator, victim, and bystander, I’ve come across a few tips that can make the process a little easier.</description>
	</item>
	<item>
		<title>Choosing an XML Schema: DocBook or DITA?</title>
		<link>http://tc.eserver.org/31157.html</link>
		<guid>http://tc.eserver.org/31157.html</guid>
		<description>If you follow the latest trends or have been to a conference recently, you may find the idea of choosing an XML schema puzzling.  Isn&apos;t the question really, &apos;How should I customize DITA to do what I want&apos;?  While there are many good reasons to choose DITA, it&apos;s not the only schema in town.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Hamilton,_Richard.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>