<?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: Testing the Limits with Google&#8217;s Patrick Copeland &#8211; Part I</title>
	<atom:link href="http://blog.utest.com/testing-the-limits-with-patrick-copeland-part-i/2010/02/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.utest.com/testing-the-limits-with-patrick-copeland-part-i/2010/02/</link>
	<description>Software Testing Community</description>
	<lastBuildDate>Wed, 08 Sep 2010 23:09:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Basharat</title>
		<link>http://blog.utest.com/testing-the-limits-with-patrick-copeland-part-i/2010/02/comment-page-1/#comment-16127</link>
		<dc:creator>Basharat</dc:creator>
		<pubDate>Mon, 12 Jul 2010 00:38:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.utest.com/?p=3671#comment-16127</guid>
		<description>Very good read.

The two things I liked int heis post are &quot;When we can’t find internal talent, community-based testing is an interesting solution to this challenge&quot; and 
70-20-10 rule for investing in technology. While the numbers are not carved in stone, the basic concept is that we invest ~70% on our existing core products, ~20% in related but new categories and ~10% on riskier bets or areas outside our existing core competencies.

Basharat</description>
		<content:encoded><![CDATA[<p>Very good read.</p>
<p>The two things I liked int heis post are &#8220;When we can’t find internal talent, community-based testing is an interesting solution to this challenge&#8221; and<br />
70-20-10 rule for investing in technology. While the numbers are not carved in stone, the basic concept is that we invest ~70% on our existing core products, ~20% in related but new categories and ~10% on riskier bets or areas outside our existing core competencies.</p>
<p>Basharat</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interview with Copeland : Clevertester</title>
		<link>http://blog.utest.com/testing-the-limits-with-patrick-copeland-part-i/2010/02/comment-page-1/#comment-16075</link>
		<dc:creator>Interview with Copeland : Clevertester</dc:creator>
		<pubDate>Wed, 30 Jun 2010 12:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.utest.com/?p=3671#comment-16075</guid>
		<description>[...] that talks about our philosophy and approach to testing at Google. Let me know what you think.   Part 1, Part 2, Part 3 (will update with link tomorrow) Posted by Patrick [...]</description>
		<content:encoded><![CDATA[<p>[...] that talks about our philosophy and approach to testing at Google. Let me know what you think.   Part 1, Part 2, Part 3 (will update with link tomorrow) Posted by Patrick [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Testing the Limits with James Whittaker &#8211; Part I &#124; Software Testing Blog</title>
		<link>http://blog.utest.com/testing-the-limits-with-patrick-copeland-part-i/2010/02/comment-page-1/#comment-16004</link>
		<dc:creator>Testing the Limits with James Whittaker &#8211; Part I &#124; Software Testing Blog</dc:creator>
		<pubDate>Tue, 22 Jun 2010 17:11:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.utest.com/?p=3671#comment-16004</guid>
		<description>[...] of the year, he held the distinction of generating the most page views… and then some guy named Patrick Copeland came along and took the lead a few months [...]</description>
		<content:encoded><![CDATA[<p>[...] of the year, he held the distinction of generating the most page views… and then some guy named Patrick Copeland came along and took the lead a few months [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Testing the Limits with Google&#8217;s Patrick Copeland &#8211; Part III &#124; Software Testing Blog</title>
		<link>http://blog.utest.com/testing-the-limits-with-patrick-copeland-part-i/2010/02/comment-page-1/#comment-14860</link>
		<dc:creator>Testing the Limits with Google&#8217;s Patrick Copeland &#8211; Part III &#124; Software Testing Blog</dc:creator>
		<pubDate>Wed, 24 Feb 2010 13:16:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.utest.com/?p=3671#comment-14860</guid>
		<description>[...] Year’s resolutions (for testing of course). In case you missed our previous interviews, here’s Part I and Part [...]</description>
		<content:encoded><![CDATA[<p>[...] Year’s resolutions (for testing of course). In case you missed our previous interviews, here’s Part I and Part [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Testing the Limits with Google&#8217;s Patrick Copeland &#8211; Part II &#124; Software Testing Blog</title>
		<link>http://blog.utest.com/testing-the-limits-with-patrick-copeland-part-i/2010/02/comment-page-1/#comment-14857</link>
		<dc:creator>Testing the Limits with Google&#8217;s Patrick Copeland &#8211; Part II &#124; Software Testing Blog</dc:creator>
		<pubDate>Tue, 23 Feb 2010 14:58:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.utest.com/?p=3671#comment-14857</guid>
		<description>[...] In Part II of our interview with Google’s Patrick Copeland, we discuss the challenges of managing a global engineering team; rewarding developers with food pellets; the difference between a good tester and a great tester; and why some companies will never launch a high-quality app. By the way, did you miss Part I of our interview? [...]</description>
		<content:encoded><![CDATA[<p>[...] In Part II of our interview with Google’s Patrick Copeland, we discuss the challenges of managing a global engineering team; rewarding developers with food pellets; the difference between a good tester and a great tester; and why some companies will never launch a high-quality app. By the way, did you miss Part I of our interview? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
