<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
maintainer-Software Development Times
<channel>
	<title>Software Development Times</title>	<link>http://tc.eserver.org/publisher/Software_Development_Times</link>
	<description>A listing of works published by Software Development Times in the field of technical communication.</description>
	<language>en-us</language>
	<atom:link href="http://tc.eserver.org/publisher/Software_Development_Times.xml" rel="self" type="application/rss+xml" />
	<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>Software Development Times</title>
		<link>http://tc.eserver.org/dir/Software_Development_Times</link>
	</image>
	<item>
		<title>The First Line of Support</title>
		<link>http://tc.eserver.org/31727.html</link>
		<guid>http://tc.eserver.org/31727.html</guid>
		<description>Customer support costs account for as much as 60 percent of a high-tech company’s total costs. Documentation is the first line of support for most customers, and customers usually use documentation to find the answer to a problem they’re having. The inevitable result of poor or nonexistent documentation is that more people try calling the customer support lines for help.</description>
	</item>
	<item>
		<title>Agile Principles Are Changing Everything</title>
		<link>http://tc.eserver.org/30707.html</link>
		<guid>http://tc.eserver.org/30707.html</guid>
		<description>There&apos;s an irony about agile development. There is no hard evidence that it produces better software, faster. And formal adoption rates, admittedly hard to measure, don&apos;t reach the 20 percent mark. Yet the ideas that underpin agile development--defining requirements incrementally, writing software in short stints, seeking customer feedback, testing code as it&apos;s written, frequent builds--have caught on like wildfire. They are widely accepted as sound development practices, even among teams that have not formally adopted them.</description>
	</item>
	<item>
		<title>Farewell, Netscape, but I Suppose It&apos;s Time</title>
		<link>http://tc.eserver.org/30708.html</link>
		<guid>http://tc.eserver.org/30708.html</guid>
		<description>Since it&apos;s been a decade since Netscape was relevant, I guess it was overdue. But that doesn&apos;t make it any easier to say goodbye to an old friend, no matter how long it&apos;s been since you had any fun together.</description>
	</item>
	<item>
		<title>Latest Isn&apos;t Always Greatest</title>
		<link>http://tc.eserver.org/19349.html</link>
		<guid>http://tc.eserver.org/19349.html</guid>
		<description>The more time I spend browsing various Web sites, the angrier I get with those developers who take liberty with the amount of software I need to view their pages and navigate their site. I realize that developers want to stay on top of what is cool and unusual and eye-catching and create a site that is visually appealing, engaging and all that. But do they realize that your average member of the browsing public doesn&apos;t care at all about these things?</description>
	</item>
</channel>
</rss>