<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Distributed Computing</title>	<link>http://tc.eserver.org/publisher/Distributed_Computing</link>
	<description>A listing of works published by Distributed Computing in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-10 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>Distributed Computing</title>
		<link>http://tc.eserver.org/dir/Distributed_Computing</link>
	</image>
	<item>
		<title>The Almighty Thud</title>
		<link>http://tc.eserver.org/32171.html</link>
		<guid>http://tc.eserver.org/32171.html</guid>
		<description>If you document everything, you are giving everything an equal weight. Do that for a complex system, and you are buried in detail. In any system there are some aspects that are more important than the others, key aspects of the system that once understood, will help someone to learn more. The art in documentation is to find how to document these aspects as clearly as possible. In this you emphasize these areas, and leave the details for the code.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Distributed_Computing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>