<?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 for BuzzPressure</title>
	<atom:link href="http://buzzpressure.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://buzzpressure.com</link>
	<description>Now with 100% more Carbon</description>
	<lastBuildDate>Tue, 17 Aug 2010 12:56:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on CTO Handbook &#8212; How to care for and feed your CTO by What&#8217;s on a mobile CTO&#8217;s desktop?</title>
		<link>http://buzzpressure.com/2008/01/08/cto-handbook-how-to-care-for-and-feed-your-cto/comment-page-1/#comment-606</link>
		<dc:creator>What&#8217;s on a mobile CTO&#8217;s desktop?</dc:creator>
		<pubDate>Tue, 17 Aug 2010 12:56:58 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/2008/01/08/cto-handbook-how-to-care-for-and-feed-your-cto/#comment-606</guid>
		<description>[...] the lines of &#8221;how to [..] feed your CTO&#8220;, and &#8220;N things you didn&#8217;t know about blogger X&#8220;, I was staring at my [...]</description>
		<content:encoded><![CDATA[<p>[...] the lines of &#8221;how to [..] feed your CTO&#8220;, and &#8220;N things you didn&#8217;t know about blogger X&#8220;, I was staring at my [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear RIM, time to pull your finger out by jfedor</title>
		<link>http://buzzpressure.com/2010/02/15/dear-rim-time-to-pull-your-finger-out/comment-page-1/#comment-552</link>
		<dc:creator>jfedor</dc:creator>
		<pubDate>Sat, 06 Mar 2010 00:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=206#comment-552</guid>
		<description>I&#039;m all for an appropriate ratio of testers to developers and would never recommend 1 to 10. I feel your pain. I don&#039;t blog much about testers but there&#039;s an older post here: &lt;a href=&quot;http://buzzpressure.com/2007/11/08/test-test-revolution/&quot; target=&quot;_blank&quot;&gt;http://buzzpressure.com/2007/11/08/test-test-revo...&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>I&#039;m all for an appropriate ratio of testers to developers and would never recommend 1 to 10. I feel your pain. I don&#039;t blog much about testers but there&#039;s an older post here: <a href="http://buzzpressure.com/2007/11/08/test-test-revolution/" target="_blank"></a><a href="http://buzzpressure.com/2007/11/08/test-test-revo.." rel="nofollow">http://buzzpressure.com/2007/11/08/test-test-revo..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear RIM, time to pull your finger out by Socorro Cimko</title>
		<link>http://buzzpressure.com/2010/02/15/dear-rim-time-to-pull-your-finger-out/comment-page-1/#comment-550</link>
		<dc:creator>Socorro Cimko</dc:creator>
		<pubDate>Fri, 05 Mar 2010 15:27:02 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=206#comment-550</guid>
		<description>Most testers find themselves outnumbered by devs. In my instance it’s almost 10 to 1. (The desirable ratio is a spent discussion I’d like to head off in this post.) Alternatively, I would like to bitch about a problem I’ve discovered as I amass more projects to test. Presuming my ten devs are extended between five projects (or app modules), every dev must pay heed simply the Feature Review/Design group meetings for the project they are responsible for. However, the tester must pay heed all five. Do you figure a problem here? Let’s do the math for a 40 hour work workweek. If every project’s Feature Review/Design meetings consume eight hours per week, every dev will have 32 hours left to write code. Every tester is provided with ZERO hours to examine code! The above scenario is not that much of an overstatement for my squad. The tester has no choice but to skip some of these meetings just to pinch in a little testing. The tester is asked to &quot;stay in the know&quot; about all projects (and how those projects mix with each other), while the dev can often focus on a single project. I conceive the above-mentioned problem is an oversight of many managers. I doubt it gets acknowledged because the testers&#039; time is being nickel and dimed out. Yet most testers and directors will assure you, “It’s a no-brainer! The tester should attend all design reappraisals and feature walkthroughs…testing should initiate as early as possible”. I agree. But it is an nonrational expectation if you staff your team like this.</description>
		<content:encoded><![CDATA[<p>Most testers find themselves outnumbered by devs. In my instance it’s almost 10 to 1. (The desirable ratio is a spent discussion I’d like to head off in this post.) Alternatively, I would like to bitch about a problem I’ve discovered as I amass more projects to test. Presuming my ten devs are extended between five projects (or app modules), every dev must pay heed simply the Feature Review/Design group meetings for the project they are responsible for. However, the tester must pay heed all five. Do you figure a problem here? Let’s do the math for a 40 hour work workweek. If every project’s Feature Review/Design meetings consume eight hours per week, every dev will have 32 hours left to write code. Every tester is provided with ZERO hours to examine code! The above scenario is not that much of an overstatement for my squad. The tester has no choice but to skip some of these meetings just to pinch in a little testing. The tester is asked to &#8220;stay in the know&#8221; about all projects (and how those projects mix with each other), while the dev can often focus on a single project. I conceive the above-mentioned problem is an oversight of many managers. I doubt it gets acknowledged because the testers&#8217; time is being nickel and dimed out. Yet most testers and directors will assure you, “It’s a no-brainer! The tester should attend all design reappraisals and feature walkthroughs…testing should initiate as early as possible”. I agree. But it is an nonrational expectation if you staff your team like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear RIM, time to pull your finger out by jfedor</title>
		<link>http://buzzpressure.com/2010/02/15/dear-rim-time-to-pull-your-finger-out/comment-page-1/#comment-529</link>
		<dc:creator>jfedor</dc:creator>
		<pubDate>Wed, 17 Feb 2010 15:58:15 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=206#comment-529</guid>
		<description>I&#039;d smash my iPhone to see that: &quot;Dance Monkey Boy!&quot; 
 
I think you&#039;re right though, this has to come from the top. Perhaps a little less NHL folly and a lot more developer love. </description>
		<content:encoded><![CDATA[<p>I&#039;d smash my iPhone to see that: &quot;Dance Monkey Boy!&quot; </p>
<p>I think you&#039;re right though, this has to come from the top. Perhaps a little less NHL folly and a lot more developer love.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear RIM, time to pull your finger out by jfedor</title>
		<link>http://buzzpressure.com/2010/02/15/dear-rim-time-to-pull-your-finger-out/comment-page-1/#comment-528</link>
		<dc:creator>jfedor</dc:creator>
		<pubDate>Wed, 17 Feb 2010 15:56:20 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=206#comment-528</guid>
		<description>Shai, you beat Google to the punch: &quot;Google&#039;s Future is in the Enterprise&quot; &lt;a href=&quot;http://www.readwriteweb.com/enterprise/2010/02/googles-eric-schmidt-at-mobile.php&quot; target=&quot;_blank&quot;&gt;http://www.readwriteweb.com/enterprise/2010/02/go...&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Shai, you beat Google to the punch: &quot;Google&#039;s Future is in the Enterprise&quot; <a href="http://www.readwriteweb.com/enterprise/2010/02/googles-eric-schmidt-at-mobile.php" target="_blank"></a><a href="http://www.readwriteweb.com/enterprise/2010/02/go.." rel="nofollow">http://www.readwriteweb.com/enterprise/2010/02/go..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear RIM, time to pull your finger out by Jim Murphy</title>
		<link>http://buzzpressure.com/2010/02/15/dear-rim-time-to-pull-your-finger-out/comment-page-1/#comment-527</link>
		<dc:creator>Jim Murphy</dc:creator>
		<pubDate>Wed, 17 Feb 2010 14:31:02 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=206#comment-527</guid>
		<description>Sorry for that trailing ). on the previous comment.  The working url is: 
&lt;a href=&quot;http://tinyurl.com/yckzcy&quot; target=&quot;_blank&quot;&gt;http://tinyurl.com/yckzcy&lt;/a&gt; 
 
More to the point would be: 
&lt;a href=&quot;http://tinyurl.com/2xzgaq&quot; target=&quot;_blank&quot;&gt;http://tinyurl.com/2xzgaq&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Sorry for that trailing ). on the previous comment.  The working url is:<br />
<a href="http://tinyurl.com/yckzcy" target="_blank">http://tinyurl.com/yckzcy</a> </p>
<p>More to the point would be:<br />
<a href="http://tinyurl.com/2xzgaq" target="_blank">http://tinyurl.com/2xzgaq</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear RIM, time to pull your finger out by Jim Murphy</title>
		<link>http://buzzpressure.com/2010/02/15/dear-rim-time-to-pull-your-finger-out/comment-page-1/#comment-526</link>
		<dc:creator>Jim Murphy</dc:creator>
		<pubDate>Wed, 17 Feb 2010 14:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=206#comment-526</guid>
		<description>Great post, Jeff.  Its great to see some of the local conversation fodder getting written down and out in the open where (hopefully) it can do some good.  As you know I&#039;ve had this very same conversation with a dozen people, half from RIM.  *Everyone* knows this is the case and in say 5 years when RIM is in serious trouble I&#039;m sure there will be no shortage of geniuses that point back to the disconnect with the developer community as a primary misstep. 
 
I want to see Jim on stage doing the &quot;developers, developers, developers...&quot; monkey boy thing(&lt;a href=&quot;http://tinyurl.com/yckzcy).&quot; target=&quot;_blank&quot;&gt;http://tinyurl.com/yckzcy).&lt;/a&gt;  But, as your post implies I worry that its more of a cultural problem.  Is encouraging an ecosystem really in the DNA of the company?   
 
I hope for its sake it is. 
 
  </description>
		<content:encoded><![CDATA[<p>Great post, Jeff.  Its great to see some of the local conversation fodder getting written down and out in the open where (hopefully) it can do some good.  As you know I&#039;ve had this very same conversation with a dozen people, half from RIM.  *Everyone* knows this is the case and in say 5 years when RIM is in serious trouble I&#039;m sure there will be no shortage of geniuses that point back to the disconnect with the developer community as a primary misstep. </p>
<p>I want to see Jim on stage doing the &quot;developers, developers, developers&#8230;&quot; monkey boy thing(<a href="http://tinyurl.com/yckzcy)." target="_blank"></a><a href="http://tinyurl.com/yckzcy)" rel="nofollow">http://tinyurl.com/yckzcy)</a>.  But, as your post implies I worry that its more of a cultural problem.  Is encouraging an ecosystem really in the DNA of the company?   </p>
<p>I hope for its sake it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear RIM, time to pull your finger out by jfedor</title>
		<link>http://buzzpressure.com/2010/02/15/dear-rim-time-to-pull-your-finger-out/comment-page-1/#comment-523</link>
		<dc:creator>jfedor</dc:creator>
		<pubDate>Tue, 16 Feb 2010 03:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=206#comment-523</guid>
		<description>I think it is deeper than that. Google is doing fine with their Java dog but it is much more of a playful pup. RIM&#039;s dog is arthritic and needs a nap. </description>
		<content:encoded><![CDATA[<p>I think it is deeper than that. Google is doing fine with their Java dog but it is much more of a playful pup. RIM&#039;s dog is arthritic and needs a nap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear RIM, time to pull your finger out by Shai</title>
		<link>http://buzzpressure.com/2010/02/15/dear-rim-time-to-pull-your-finger-out/comment-page-1/#comment-522</link>
		<dc:creator>Shai</dc:creator>
		<pubDate>Tue, 16 Feb 2010 02:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=206#comment-522</guid>
		<description>right on, I wrote a related blog post as well, focusing on why I think Android is big trouble for RIM - &lt;a href=&quot;http://shaigoldman.wordpress.com/2010/02/16/rimblackberry-killer/&quot; target=&quot;_blank&quot;&gt;http://shaigoldman.wordpress.com/2010/02/16/rimbl...&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>right on, I wrote a related blog post as well, focusing on why I think Android is big trouble for RIM &#8211; <a href="http://shaigoldman.wordpress.com/2010/02/16/rimblackberry-killer/" target="_blank"></a><a href="http://shaigoldman.wordpress.com/2010/02/16/rimbl.." rel="nofollow">http://shaigoldman.wordpress.com/2010/02/16/rimbl..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dear RIM, time to pull your finger out by uberVU - social comments</title>
		<link>http://buzzpressure.com/2010/02/15/dear-rim-time-to-pull-your-finger-out/comment-page-1/#comment-521</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Tue, 16 Feb 2010 02:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=206#comment-521</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by WatTechDigest: Two local takes on RIM: 1) Jeff Fedor http://bit.ly/9ki2jI 2) Christopher Reid http://bit.ly/9csTkL...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by WatTechDigest: Two local takes on RIM: 1) Jeff Fedor <a href="http://bit.ly/9ki2jI" rel="nofollow">http://bit.ly/9ki2jI</a> 2) Christopher Reid <a href="http://bit.ly/9csTkL.." rel="nofollow">http://bit.ly/9csTkL..</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
