<?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: What makes a grade &#8220;A&#8221; developer</title>
	<atom:link href="http://blog.kriskemper.com/2008/07/14/what-makes-a-grade-a-developer/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kriskemper.com/2008/07/14/what-makes-a-grade-a-developer/</link>
	<description>Thoughtworker, Agile Philosopher, Hero</description>
	<lastBuildDate>Sun, 11 Sep 2011 04:15:23 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: The Punch Barrel / What makes a grade “A” developer</title>
		<link>http://blog.kriskemper.com/2008/07/14/what-makes-a-grade-a-developer/comment-page-1/#comment-80</link>
		<dc:creator>The Punch Barrel / What makes a grade “A” developer</dc:creator>
		<pubDate>Tue, 15 Jul 2008 08:31:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kriskemper.com/2008/07/14/what-makes-a-grade-a-developer/#comment-80</guid>
		<description>[...] Kris Kemper » Blog Archive » What makes a grade “A” developer [...]</description>
		<content:encoded><![CDATA[<p>[...] Kris Kemper » Blog Archive » What makes a grade “A” developer [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hendrikch</title>
		<link>http://blog.kriskemper.com/2008/07/14/what-makes-a-grade-a-developer/comment-page-1/#comment-79</link>
		<dc:creator>hendrikch</dc:creator>
		<pubDate>Tue, 15 Jul 2008 06:17:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kriskemper.com/2008/07/14/what-makes-a-grade-a-developer/#comment-79</guid>
		<description>well said...
I like the part where you said: I generally don’t differentiate between missed requirements and technical bugs - as a developer, I play an important role in making sure that it is understood and agreed upon as to what I will be making.</description>
		<content:encoded><![CDATA[<p>well said&#8230;<br />
I like the part where you said: I generally don’t differentiate between missed requirements and technical bugs &#8211; as a developer, I play an important role in making sure that it is understood and agreed upon as to what I will be making.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

