<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Become an Expert: Making Ideas Stick</title>
	<atom:link href="http://softwarecreation.org/2010/how-to-become-an-expert-making-ideas-stick/feed/" rel="self" type="application/rss+xml" />
	<link>http://softwarecreation.org/2010/how-to-become-an-expert-making-ideas-stick/</link>
	<description>What are the forces behind software development?</description>
	<lastBuildDate>Sun, 22 Aug 2010 05:18:12 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Emma</title>
		<link>http://softwarecreation.org/2010/how-to-become-an-expert-making-ideas-stick/comment-page-1/#comment-35511</link>
		<dc:creator>Emma</dc:creator>
		<pubDate>Thu, 29 Apr 2010 15:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://softwarecreation.org/?p=106#comment-35511</guid>
		<description>This issue of how programmers should communicate with clients is a very interesting one. I especially like what you say about the Curse of Knowledge: as a writer from a non-tech background doing research for tech writing, I frequently come across literature by experts who simply cannot imagine what it might be like to know no principles, with the result that their explanations remain obscure. In the spirit of sharing tips on effective communication, here are a couple of blogs which discuss the client-developer relations:

http://blog.bitzesty.com/what-to-expect-from-an-agile-web-development

and 

http://blog.bitzesty.com/5-ways-to-keep-a-web-project-on-the-rails-0</description>
		<content:encoded><![CDATA[<p>This issue of how programmers should communicate with clients is a very interesting one. I especially like what you say about the Curse of Knowledge: as a writer from a non-tech background doing research for tech writing, I frequently come across literature by experts who simply cannot imagine what it might be like to know no principles, with the result that their explanations remain obscure. In the spirit of sharing tips on effective communication, here are a couple of blogs which discuss the client-developer relations:</p>
<p><a href="http://blog.bitzesty.com/what-to-expect-from-an-agile-web-development" rel="nofollow">http://blog.bitzesty.com/what-to-expect-from-an-agile-web-development</a></p>
<p>and </p>
<p><a href="http://blog.bitzesty.com/5-ways-to-keep-a-web-project-on-the-rails-0" rel="nofollow">http://blog.bitzesty.com/5-ways-to-keep-a-web-project-on-the-rails-0</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andries Inzé</title>
		<link>http://softwarecreation.org/2010/how-to-become-an-expert-making-ideas-stick/comment-page-1/#comment-32995</link>
		<dc:creator>Andries Inzé</dc:creator>
		<pubDate>Sun, 31 Jan 2010 09:22:36 +0000</pubDate>
		<guid isPermaLink="false">http://softwarecreation.org/?p=106#comment-32995</guid>
		<description>Excellent summary of an excellent book.</description>
		<content:encoded><![CDATA[<p>Excellent summary of an excellent book.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Antônio Siqueira</title>
		<link>http://softwarecreation.org/2010/how-to-become-an-expert-making-ideas-stick/comment-page-1/#comment-32719</link>
		<dc:creator>William Antônio Siqueira</dc:creator>
		<pubDate>Thu, 21 Jan 2010 12:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://softwarecreation.org/?p=106#comment-32719</guid>
		<description>Very Nice!

Sometimes some smart people have good ideas, but they don&#039;t know how to sell/transmite them!

Great post.</description>
		<content:encoded><![CDATA[<p>Very Nice!</p>
<p>Sometimes some smart people have good ideas, but they don&#8217;t know how to sell/transmite them!</p>
<p>Great post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
