<?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: Focus.</title>
	<atom:link href="http://gluue.com/2010/08/focus/feed/" rel="self" type="application/rss+xml" />
	<link>http://gluue.com/2010/08/focus/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 17 Mar 2026 18:34:31 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.8.41</generator>
	<item>
		<title>By: Joe</title>
		<link>http://gluue.com/2010/08/focus/comment-page-1/#comment-5177</link>
		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Fri, 06 Aug 2010 17:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://gluue.com/?p=2328#comment-5177</guid>
		<description><![CDATA[Chairman Gruber weighs in. http://daringfireball.net/linked/2010/08/06/google-wave-failure]]></description>
		<content:encoded><![CDATA[<p>Chairman Gruber weighs in. <a href="http://daringfireball.net/linked/2010/08/06/google-wave-failure" rel="nofollow">http://daringfireball.net/linked/2010/08/06/google-wave-failure</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://gluue.com/2010/08/focus/comment-page-1/#comment-5159</link>
		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Fri, 06 Aug 2010 03:41:30 +0000</pubDate>
		<guid isPermaLink="false">http://gluue.com/?p=2328#comment-5159</guid>
		<description><![CDATA[It&#039;s an absolutely good point Arnold. I hope Paste always takes risks, and goes with our gut. This job would cease to be fun if we didn&#039;t. But... I can&#039;t even tell you how many projects we&#039;ve killed internally this year because they didn&#039;t live up to our standards. Not just dabbling half day efforts, -sometimes many months worth of development down the drain. Not because we quit, or not (hopefully) because we lacked vision, - but because we pursued it far enough to know if we could be proud of it. It&#039;s something I hope every company does. It comes from being an ombudsman for your customer at the last minute. No matter how many hours, no matter how many egos, if we can&#039;t go to sleep at night thinking it&#039;s going to make a positive dent in our user&#039;s lives, we don&#039;t put it out. That&#039;s not to say everything we do is perfect, -but we&#039;re setting our standards at a certain level regardless of our resources. Since Google is a couple billion times bigger than we are, -are they killing a couple billion more projects a year that we are?]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s an absolutely good point Arnold. I hope Paste always takes risks, and goes with our gut. This job would cease to be fun if we didn&#8217;t. But&#8230; I can&#8217;t even tell you how many projects we&#8217;ve killed internally this year because they didn&#8217;t live up to our standards. Not just dabbling half day efforts, -sometimes many months worth of development down the drain. Not because we quit, or not (hopefully) because we lacked vision, &#8211; but because we pursued it far enough to know if we could be proud of it. It&#8217;s something I hope every company does. It comes from being an ombudsman for your customer at the last minute. No matter how many hours, no matter how many egos, if we can&#8217;t go to sleep at night thinking it&#8217;s going to make a positive dent in our user&#8217;s lives, we don&#8217;t put it out. That&#8217;s not to say everything we do is perfect, -but we&#8217;re setting our standards at a certain level regardless of our resources. Since Google is a couple billion times bigger than we are, -are they killing a couple billion more projects a year that we are?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arnold Gamboa</title>
		<link>http://gluue.com/2010/08/focus/comment-page-1/#comment-5153</link>
		<dc:creator><![CDATA[Arnold Gamboa]]></dc:creator>
		<pubDate>Fri, 06 Aug 2010 01:59:45 +0000</pubDate>
		<guid isPermaLink="false">http://gluue.com/?p=2328#comment-5153</guid>
		<description><![CDATA[I guess the mark of a great company is its willingness to take risks. Playing it safe is normal. Risk taking is extraordinary.]]></description>
		<content:encoded><![CDATA[<p>I guess the mark of a great company is its willingness to take risks. Playing it safe is normal. Risk taking is extraordinary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://gluue.com/2010/08/focus/comment-page-1/#comment-5141</link>
		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Thu, 05 Aug 2010 19:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://gluue.com/?p=2328#comment-5141</guid>
		<description><![CDATA[Ryan, -really well thought out response. You&#039;re of course totally right that when you fail you should admit it honestly, and move on. You can actually _gain_ respect by doing it like that. But Wave was only one example really -the freshest one. What about the other 75 things Google is into now? Are they going to be able to be really truly great at all of them? Shouldn&#039;t they maybe do fewer things, but do those things really well? The decisions to fail in public(Google) or fail in private(Apple) may be an internal politics thing, or an honesty thing... But what about working to create a situation where failing is less likely in the first place?]]></description>
		<content:encoded><![CDATA[<p>Ryan, -really well thought out response. You&#8217;re of course totally right that when you fail you should admit it honestly, and move on. You can actually <em>gain</em> respect by doing it like that. But Wave was only one example really -the freshest one. What about the other 75 things Google is into now? Are they going to be able to be really truly great at all of them? Shouldn&#8217;t they maybe do fewer things, but do those things really well? The decisions to fail in public(Google) or fail in private(Apple) may be an internal politics thing, or an honesty thing&#8230; But what about working to create a situation where failing is less likely in the first place?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Giglio</title>
		<link>http://gluue.com/2010/08/focus/comment-page-1/#comment-5140</link>
		<dc:creator><![CDATA[Ryan Giglio]]></dc:creator>
		<pubDate>Thu, 05 Aug 2010 19:19:41 +0000</pubDate>
		<guid isPermaLink="false">http://gluue.com/?p=2328#comment-5140</guid>
		<description><![CDATA[I would agree with the mistrust thing if they released Wave as a full out product, but it was in &quot;preview&quot; (not even alpha or beta) for almost all of its life in the wild. I know that Google puts badges like that on all their products when they first release them, but in this case I think they were extra careful to make sure people were aware that it was really just an experiment. I was always looking at Wave as a really complex tech demo of the things HTML5 could do - it was one of the first big mainstream HTML5 web apps.

Also, I think Google made a very calculated judgement call with this. We all know that Wave really fell short in its adoption. If it had taken off and was being used in the main workflow of a lot of people, I don&#039;t think they would have dropped support for it for fear of a large public backlash. On Twitter the response has mostly been &quot;well, finally&quot; rather than regret or annoyance. Everyone recognized Wave was a valiant effort that wasn&#039;t working. Companies don&#039;t often give up on products they spent a lot of money on, and I think if Google saw any light at the end of the tunnel for Wave they would have kept it alive.

I don&#039;t think it hurts Google&#039;s credibility to admit &quot;we thought this would be really cool, it&#039;s not working, we messed up.&quot; I&#039;d much rather companies admit they messed up and move on than take the Apple route (most likely &quot;this is so cool you all were stupid for not using it when it was out there&quot;). I give them a lot of credit for ceasing development on it, rather than drag it sadly along way past its lifespan.]]></description>
		<content:encoded><![CDATA[<p>I would agree with the mistrust thing if they released Wave as a full out product, but it was in &#8220;preview&#8221; (not even alpha or beta) for almost all of its life in the wild. I know that Google puts badges like that on all their products when they first release them, but in this case I think they were extra careful to make sure people were aware that it was really just an experiment. I was always looking at Wave as a really complex tech demo of the things HTML5 could do &#8211; it was one of the first big mainstream HTML5 web apps.</p>
<p>Also, I think Google made a very calculated judgement call with this. We all know that Wave really fell short in its adoption. If it had taken off and was being used in the main workflow of a lot of people, I don&#8217;t think they would have dropped support for it for fear of a large public backlash. On Twitter the response has mostly been &#8220;well, finally&#8221; rather than regret or annoyance. Everyone recognized Wave was a valiant effort that wasn&#8217;t working. Companies don&#8217;t often give up on products they spent a lot of money on, and I think if Google saw any light at the end of the tunnel for Wave they would have kept it alive.</p>
<p>I don&#8217;t think it hurts Google&#8217;s credibility to admit &#8220;we thought this would be really cool, it&#8217;s not working, we messed up.&#8221; I&#8217;d much rather companies admit they messed up and move on than take the Apple route (most likely &#8220;this is so cool you all were stupid for not using it when it was out there&#8221;). I give them a lot of credit for ceasing development on it, rather than drag it sadly along way past its lifespan.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://gluue.com/2010/08/focus/comment-page-1/#comment-5139</link>
		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Thu, 05 Aug 2010 19:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://gluue.com/?p=2328#comment-5139</guid>
		<description><![CDATA[Gabe, I&#039;m not arguing that it can&#039;t be profitable short term. I just wonder what the long term effect is. Let&#039;s say there are X users who are enticed into using a Google service based on brand credibility. When the service is half-baked, or shut down pre-emptively how many people lose respect for the brand based on the poor experience? 1%? 5%? OK, now multiply that times 10 new &quot;experiments&quot; a year. Now multiply that times 10 years. 20 years. For the most part I&#039;m a Google fan, but I do worry they do more harm than good by allowing their &quot;experiments&quot; into the wild. At the very least they should be more forthcoming about what is a strong initiative, and what is a hobby.]]></description>
		<content:encoded><![CDATA[<p>Gabe, I&#8217;m not arguing that it can&#8217;t be profitable short term. I just wonder what the long term effect is. Let&#8217;s say there are X users who are enticed into using a Google service based on brand credibility. When the service is half-baked, or shut down pre-emptively how many people lose respect for the brand based on the poor experience? 1%? 5%? OK, now multiply that times 10 new &#8220;experiments&#8221; a year. Now multiply that times 10 years. 20 years. For the most part I&#8217;m a Google fan, but I do worry they do more harm than good by allowing their &#8220;experiments&#8221; into the wild. At the very least they should be more forthcoming about what is a strong initiative, and what is a hobby.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabe</title>
		<link>http://gluue.com/2010/08/focus/comment-page-1/#comment-5138</link>
		<dc:creator><![CDATA[Gabe]]></dc:creator>
		<pubDate>Thu, 05 Aug 2010 18:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://gluue.com/?p=2328#comment-5138</guid>
		<description><![CDATA[You forgot space:) http://bits.blogs.nytimes.com/2010/07/27/meet-googles-space-commander/

---

&quot;So is the “Make lots of stuff, and see what sticks” a viable way to run a long term business? &quot;

Consider all this Google&#039;s internal VC fund. If you figure a project requires 10 engineers and each engineer costs $200K a year, then that&#039;s $2 million per year per project. If they have 20 projects a year, then that&#039;s 40 million a year - a drop in the bucker for Google - they take a flier on something with potential for big gains and overall, it&#039;s a small price to pay to demonstrate to your ambitious, talented workforce that you&#039;re willing to go out on a limb and take risks.

Even if you want to tack on another 40 million to the development costs, we&#039;re still not talking huge sums on a per project basis compared to the costs manufacturing firms put into new products]]></description>
		<content:encoded><![CDATA[<p>You forgot space:) <a href="http://bits.blogs.nytimes.com/2010/07/27/meet-googles-space-commander/" rel="nofollow">http://bits.blogs.nytimes.com/2010/07/27/meet-googles-space-commander/</a></p>
<p>&#8212;-</p>
<p>&#8220;So is the “Make lots of stuff, and see what sticks” a viable way to run a long term business? &#8220;</p>
<p>Consider all this Google&#8217;s internal VC fund. If you figure a project requires 10 engineers and each engineer costs $200K a year, then that&#8217;s $2 million per year per project. If they have 20 projects a year, then that&#8217;s 40 million a year &#8211; a drop in the bucker for Google &#8211; they take a flier on something with potential for big gains and overall, it&#8217;s a small price to pay to demonstrate to your ambitious, talented workforce that you&#8217;re willing to go out on a limb and take risks.</p>
<p>Even if you want to tack on another 40 million to the development costs, we&#8217;re still not talking huge sums on a per project basis compared to the costs manufacturing firms put into new products</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 251/254 objects using disk

 Served from: gluue.com @ 2026-04-22 00:14:53 by W3 Total Cache -->