<?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: Why developers don’t find defects</title>
	<atom:link href="http://www.testingthefuture.net/2010/01/why-developers-don%e2%80%99t-find-defects/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.testingthefuture.net/2010/01/why-developers-don%e2%80%99t-find-defects/</link>
	<description></description>
	<lastBuildDate>Wed, 01 Feb 2012 06:10:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dave Nicolette</title>
		<link>http://www.testingthefuture.net/2010/01/why-developers-don%e2%80%99t-find-defects/comment-page-1/#comment-741</link>
		<dc:creator>Dave Nicolette</dc:creator>
		<pubDate>Sun, 31 Jan 2010 15:57:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.testingthefuture.net/?p=867#comment-741</guid>
		<description>Good points, clearly expressed. 

I sometimes express the difference in mindset between developers and testers this way: Developers want to prove their code works, and testers are looking for ways the code might break (including ways the code doesn&#039;t satisfy users, even if it is functional). 

Not meaning to get on anyone&#039;s bad side, I have to say I don&#039;t think it is a big leap for a developer to switch gears and look for weaknesses in his/her code. The fact there is a need for testing specialists may be a &quot;smell&quot; suggesting possible areas of improvement for software developers&#039; skill sets (or mindsets, as the case may be). The two &quot;professions&quot; of developer and tester should merge into one, IMHO.</description>
		<content:encoded><![CDATA[<p>Good points, clearly expressed. </p>
<p>I sometimes express the difference in mindset between developers and testers this way: Developers want to prove their code works, and testers are looking for ways the code might break (including ways the code doesn&#8217;t satisfy users, even if it is functional). </p>
<p>Not meaning to get on anyone&#8217;s bad side, I have to say I don&#8217;t think it is a big leap for a developer to switch gears and look for weaknesses in his/her code. The fact there is a need for testing specialists may be a &#8220;smell&#8221; suggesting possible areas of improvement for software developers&#8217; skill sets (or mindsets, as the case may be). The two &#8220;professions&#8221; of developer and tester should merge into one, IMHO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Echlin</title>
		<link>http://www.testingthefuture.net/2010/01/why-developers-don%e2%80%99t-find-defects/comment-page-1/#comment-737</link>
		<dc:creator>William Echlin</dc:creator>
		<pubDate>Tue, 19 Jan 2010 14:36:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.testingthefuture.net/?p=867#comment-737</guid>
		<description>Fascinating. I think a lot is made about the differences between the mindset of the software tester and the software developer. We&#039;re all human beings though and I know I make mistakes as a software tester just as software developers do. 
	
Personally I think a lot of it depends on what your main objective is. Developers are focused on delivering code. Testers focus on finding software defects. If developers stopped writing code and set their objective to finding software defects then I&#039;m sure that they would make great software testers too. It&#039;s just re-aligning your objective, and as mentioned changing your viewpoints. Would be interesting to see if software testers could make good developers with a little bit of training. 

Perhaps that&#039;s one of the things I really like about software testing. With software testing you are driven to think more about your viewpoint and objectives. With software testing you have to look for problems from different viewpoints in order to make sure you help drive the whole team towards delivering the highest quality possible. In software testing seeing things from the developers, users and project management&#039;s perspective is essential.

William Echlin
&lt;a href=&quot;http://www.softwaretesting.net&quot; rel=&quot;nofollow&quot;&gt;www.SoftwareTesting.net&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Fascinating. I think a lot is made about the differences between the mindset of the software tester and the software developer. We&#8217;re all human beings though and I know I make mistakes as a software tester just as software developers do. </p>
<p>Personally I think a lot of it depends on what your main objective is. Developers are focused on delivering code. Testers focus on finding software defects. If developers stopped writing code and set their objective to finding software defects then I&#8217;m sure that they would make great software testers too. It&#8217;s just re-aligning your objective, and as mentioned changing your viewpoints. Would be interesting to see if software testers could make good developers with a little bit of training. </p>
<p>Perhaps that&#8217;s one of the things I really like about software testing. With software testing you are driven to think more about your viewpoint and objectives. With software testing you have to look for problems from different viewpoints in order to make sure you help drive the whole team towards delivering the highest quality possible. In software testing seeing things from the developers, users and project management&#8217;s perspective is essential.</p>
<p>William Echlin<br />
<a href="http://www.softwaretesting.net" rel="nofollow">http://www.SoftwareTesting.net</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2010-01-18 &#187; ????&#8212;-?????</title>
		<link>http://www.testingthefuture.net/2010/01/why-developers-don%e2%80%99t-find-defects/comment-page-1/#comment-736</link>
		<dc:creator>links for 2010-01-18 &#187; ????&#8212;-?????</dc:creator>
		<pubDate>Mon, 18 Jan 2010 16:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.testingthefuture.net/?p=867#comment-736</guid>
		<description>[...] Software Testing and more » Blog Archive » Why developers don’t find defects (tags: test develop software) [...]</description>
		<content:encoded><![CDATA[<p>[...] Software Testing and more » Blog Archive » Why developers don’t find defects (tags: test develop software) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bert Veldman</title>
		<link>http://www.testingthefuture.net/2010/01/why-developers-don%e2%80%99t-find-defects/comment-page-1/#comment-735</link>
		<dc:creator>Bert Veldman</dc:creator>
		<pubDate>Mon, 18 Jan 2010 10:15:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.testingthefuture.net/?p=867#comment-735</guid>
		<description>Thanks for this explaning blog!
Beside my job as testcoordinator, I also develop my own tools and websites. And I must say that it is hard to test my own work. I have to sit back, put on my testcap and look at the results of my developing with a different mindset. Only in this way I can tell what is still not correct or should be improved. 
I always encourage testers to develop their developing skills. This help them look to the SuT with a completer view.
And it is a comfortable thought that I can always blame my DLPFC for not finding these nasty bugs ;-)</description>
		<content:encoded><![CDATA[<p>Thanks for this explaning blog!<br />
Beside my job as testcoordinator, I also develop my own tools and websites. And I must say that it is hard to test my own work. I have to sit back, put on my testcap and look at the results of my developing with a different mindset. Only in this way I can tell what is still not correct or should be improved.<br />
I always encourage testers to develop their developing skills. This help them look to the SuT with a completer view.<br />
And it is a comfortable thought that I can always blame my DLPFC for not finding these nasty bugs <img src='http://www.testingthefuture.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Software Testing and more » Blog Archive » Why developers don’t find defects -- Topsy.com</title>
		<link>http://www.testingthefuture.net/2010/01/why-developers-don%e2%80%99t-find-defects/comment-page-1/#comment-734</link>
		<dc:creator>Tweets that mention Software Testing and more » Blog Archive » Why developers don’t find defects -- Topsy.com</dc:creator>
		<pubDate>Mon, 18 Jan 2010 09:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.testingthefuture.net/?p=867#comment-734</guid>
		<description>[...] This post was mentioned on Twitter by Ewald Roodenrijs and Andreas Prins, Ivo Bronsveld. Ivo Bronsveld said: RT @ewaldroodenrijs: New try: New blog post » Why developers don’t find defects: http://ow.ly/XBxb. Thanks to @testingqa #softwaretesting [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Ewald Roodenrijs and Andreas Prins, Ivo Bronsveld. Ivo Bronsveld said: RT @ewaldroodenrijs: New try: New blog post » Why developers don’t find defects: <a href="http://ow.ly/XBxb" rel="nofollow">http://ow.ly/XBxb</a>. Thanks to @testingqa #softwaretesting [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

