<?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: Changing Developer Behaviour, Part II</title>
	<atom:link href="http://misko.hevery.com/2008/09/10/changing-developer-behaviour-part-ii/feed/" rel="self" type="application/rss+xml" />
	<link>http://misko.hevery.com/2008/09/10/changing-developer-behaviour-part-ii/</link>
	<description>Testability Explorer</description>
	<lastBuildDate>Fri, 30 Jul 2010 03:59:03 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Roddy</title>
		<link>http://misko.hevery.com/2008/09/10/changing-developer-behaviour-part-ii/comment-page-1/#comment-171</link>
		<dc:creator>Mark Roddy</dc:creator>
		<pubDate>Fri, 12 Sep 2008 20:36:29 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?p=208#comment-171</guid>
		<description>I like this idea a lot.  I&#039;ve been trying to figure out how to get people in my group to write more (in some cases any at all) unit tests in our code base.  I think tracking code coverage of the tests over time could help with this.  Though there&#039;s one thing I would worry about:
&quot;The screaming will stop as soon as each person has received individual attention to learn how to code correctly. &quot;

Some resistance has been very ego driven.  I hear statements like &quot;I&#039;ve been programming for X years just fine.  I know what I&#039;m doing.&quot; to justify not testing.  Essentially, proposed process changes are taken as a personal accustations against their abilities.  My first thought was that some people would claim that they already know how to &quot;code correctly&quot; and be come even more resistant.

-Mark</description>
		<content:encoded><![CDATA[<p>I like this idea a lot.  I&#8217;ve been trying to figure out how to get people in my group to write more (in some cases any at all) unit tests in our code base.  I think tracking code coverage of the tests over time could help with this.  Though there&#8217;s one thing I would worry about:<br />
&#8220;The screaming will stop as soon as each person has received individual attention to learn how to code correctly. &#8221;</p>
<p>Some resistance has been very ego driven.  I hear statements like &#8220;I&#8217;ve been programming for X years just fine.  I know what I&#8217;m doing.&#8221; to justify not testing.  Essentially, proposed process changes are taken as a personal accustations against their abilities.  My first thought was that some people would claim that they already know how to &#8220;code correctly&#8221; and be come even more resistant.</p>
<p>-Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Changing Developer Behavior - Part 1 &#124; Miško Hevery</title>
		<link>http://misko.hevery.com/2008/09/10/changing-developer-behaviour-part-ii/comment-page-1/#comment-149</link>
		<dc:creator>Changing Developer Behavior - Part 1 &#124; Miško Hevery</dc:creator>
		<pubDate>Wed, 10 Sep 2008 15:39:47 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?p=208#comment-149</guid>
		<description>[...] as well as socially acceptable.  But this isn&#8217;t enough: it must be constantly reinforced.  Part II of this series will present ways to make progress toward change highly visible yet subtly [...]</description>
		<content:encoded><![CDATA[<p>[...] as well as socially acceptable.  But this isn&#8217;t enough: it must be constantly reinforced.  Part II of this series will present ways to make progress toward change highly visible yet subtly [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
