<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Kelly, William T.</title>	<link>http://tc.eserver.org/authors/Kelly,_William_T.</link>
	<description>A bibliography of works by Kelly, William T. 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>Kelly, William T.</title>
		<link>http://tc.eserver.org/dir/Kelly,_William_T.</link>
	</image>
	<item>
		<title>How Google Wave Can Drown Technical Writers</title>
		<link>http://tc.eserver.org/35379.html</link>
		<guid>http://tc.eserver.org/35379.html</guid>
		<description>The impending launch of Google Wave is something for every technical writer to watch. Because if they have been doing their job the same way from day one, then Google Wave&apos;s undertow is going to pull them down into the surf.&#xD;&#xD;However, if they are embracing online collaborations tools, instant messaging, and related technologies then they are going to think Google Wave is game changer for technical communications because it offers a new range of communications and collaborations options.</description>
	</item>
	<item>
		<title>Leaving Technical Writing</title>
		<link>http://tc.eserver.org/32821.html</link>
		<guid>http://tc.eserver.org/32821.html</guid>
		<description>It&apos;s time to turn out the lights. I&apos;ve had a great run as a technical writer and consultant but it&apos;s time to leave the profession. In some ways I&apos;ve long outgrown technical writing because client needs as a consultant challenged me and pushed me to become more than just a technical writer.</description>
	</item>
	<item>
		<title>Adjust Your Documentation Plan for .NET</title>
		<link>http://tc.eserver.org/29368.html</link>
		<guid>http://tc.eserver.org/29368.html</guid>
		<description>Developing in the .NET environment requires internal documentation changes. Learn how to adjust your documentation plan so that it encompasses additional elements, such as the needs of mobile users.</description>
	</item>
	<item>
		<title>The Hidden Relationship Between Project Managers and Technical Writers</title>
		<link>http://tc.eserver.org/29336.html</link>
		<guid>http://tc.eserver.org/29336.html</guid>
		<description>Want to know the secret to better quality documentation and improved software design? Will Kelly outlines how the key is an effective relationship between project managers and technical writers.</description>
	</item>
	<item>
		<title>Strategies When Hiring a Technical Writer</title>
		<link>http://tc.eserver.org/29332.html</link>
		<guid>http://tc.eserver.org/29332.html</guid>
		<description>This article offers tips for project and development managers hiring a technical writer to document a software development project.</description>
	</item>
	<item>
		<title>Tips for Documenting an XML DTD</title>
		<link>http://tc.eserver.org/29342.html</link>
		<guid>http://tc.eserver.org/29342.html</guid>
		<description>XML-based development projects often require the development of a Document Type Definition (DTD), which defines the XML code used in an XML document or application. Even if you are customizing an existing DTD like the DocBook DTD, documenting the DTD is a best practice for a number of reasons, including:Providing documentation</description>
	</item>
	<item>
		<title>Document your Database Project to Capture Relevant Info</title>
		<link>http://tc.eserver.org/26262.html</link>
		<guid>http://tc.eserver.org/26262.html</guid>
		<description>Documenting a database during its development is a best practice to ensure that the organizational schema, data objects, and other related information are captured for future reference.</description>
	</item>
	<item>
		<title>Kelly&apos;s Laws of Technical Writing (retro version)</title>
		<link>http://tc.eserver.org/24851.html</link>
		<guid>http://tc.eserver.org/24851.html</guid>
		<description>A reaction to the dysfunction of technical writing in the modern workplace.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Kelly,_William_T..xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>