<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Scherf, Ryan</title>	<link>http://tc.eserver.org/authors/Scherf,_Ryan</link>
	<description>A bibliography of works by Scherf, Ryan 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>Scherf, Ryan</title>
		<link>http://tc.eserver.org/dir/Scherf,_Ryan</link>
	</image>
	<item>
		<title>How To Effectively Communicate With Developers</title>
		<link>http://tc.eserver.org/35373.html</link>
		<guid>http://tc.eserver.org/35373.html</guid>
		<description>If you have ever worked with a developer or a development team, this article will probably strike close to home. As designers, we work with dozens of developers across the globe each year. Some of us are fortunate enough to find a gem; a developer that just gets it. A developer that you feel is on your same wavelength in terms of what needs to be accomplished with the user interface, and what it needs to happen. Most often, however, we find developers that we generally don’t see eye to eye with.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Scherf,_Ryan.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>