<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Scaling lessons from Google&#8217;s CIO</title>
	<atom:link href="http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 20:41:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Frank Pasquale</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-691467</link>
		<dc:creator><![CDATA[Frank Pasquale]]></dc:creator>
		<pubDate>Thu, 24 Nov 2011 02:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-691467</guid>
		<description><![CDATA[“The Industrial Age, when specialization ruled, is over” http://t.co/gwQNlaZf]]></description>
		<content:encoded><![CDATA[<p>“The Industrial Age, when specialization ruled, is over” <a href="http://t.co/gwQNlaZf" rel="nofollow">http://t.co/gwQNlaZf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Pasquale</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-691362</link>
		<dc:creator><![CDATA[Frank Pasquale]]></dc:creator>
		<pubDate>Thu, 24 Nov 2011 01:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-691362</guid>
		<description><![CDATA[RT @timohannay: Scaling lessons from Google’s CIO. Hire generalists, not specialists: http://t.co/Xdnx6mw5 (HT @spanx)]]></description>
		<content:encoded><![CDATA[<p>RT @timohannay: Scaling lessons from Google’s CIO. Hire generalists, not specialists: <a href="http://t.co/Xdnx6mw5" rel="nofollow">http://t.co/Xdnx6mw5</a> (HT @spanx)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hilary Spencer</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-691260</link>
		<dc:creator><![CDATA[Hilary Spencer]]></dc:creator>
		<pubDate>Thu, 24 Nov 2011 00:54:54 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-691260</guid>
		<description><![CDATA[RT @timohannay: Scaling lessons from Google’s CIO. Hire generalists, not specialists: http://t.co/Xdnx6mw5 (HT @spanx)]]></description>
		<content:encoded><![CDATA[<p>RT @timohannay: Scaling lessons from Google’s CIO. Hire generalists, not specialists: <a href="http://t.co/Xdnx6mw5" rel="nofollow">http://t.co/Xdnx6mw5</a> (HT @spanx)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shan Rahulan</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-685512</link>
		<dc:creator><![CDATA[Shan Rahulan]]></dc:creator>
		<pubDate>Tue, 22 Nov 2011 16:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-685512</guid>
		<description><![CDATA[Disaster porn and the webscale age. A change of thinking required?  http://t.co/gNPAP9LD #IN]]></description>
		<content:encoded><![CDATA[<p>Disaster porn and the webscale age. A change of thinking required?  <a href="http://t.co/gNPAP9LD" rel="nofollow">http://t.co/gNPAP9LD</a> #IN</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Carrier</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-684898</link>
		<dc:creator><![CDATA[Nick Carrier]]></dc:creator>
		<pubDate>Tue, 22 Nov 2011 10:11:30 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-684898</guid>
		<description><![CDATA[Scaling lessons from Google&#039;s CIO http://t.co/5TTrZ7bt]]></description>
		<content:encoded><![CDATA[<p>Scaling lessons from Google&#8217;s CIO <a href="http://t.co/5TTrZ7bt" rel="nofollow">http://t.co/5TTrZ7bt</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddie</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-660385</link>
		<dc:creator><![CDATA[Eddie]]></dc:creator>
		<pubDate>Sat, 01 Oct 2011 00:27:12 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-660385</guid>
		<description><![CDATA[Stacey, this is a great article, you are truly one of the best journalists in this business and you often discover very useful and pertinent nuggets of things to think about. Thank you for your great efforts at Gigaom!  btw, this quote excerpted:

&gt; ... realization that when you are building at scale, you are at the edge of
&gt; the known world. 

This makes me think of Nassim Taleb&#039;s Black Swan concept construed mostly onto the financial community (unknown unknowns)!]]></description>
		<content:encoded><![CDATA[<p>Stacey, this is a great article, you are truly one of the best journalists in this business and you often discover very useful and pertinent nuggets of things to think about. Thank you for your great efforts at Gigaom!  btw, this quote excerpted:</p>
<p>&gt; &#8230; realization that when you are building at scale, you are at the edge of<br />
&gt; the known world. </p>
<p>This makes me think of Nassim Taleb&#8217;s Black Swan concept construed mostly onto the financial community (unknown unknowns)!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-660268</link>
		<dc:creator><![CDATA[Max]]></dc:creator>
		<pubDate>Fri, 30 Sep 2011 17:44:30 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-660268</guid>
		<description><![CDATA[excellent article]]></description>
		<content:encoded><![CDATA[<p>excellent article</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-660186</link>
		<dc:creator><![CDATA[Ryan]]></dc:creator>
		<pubDate>Fri, 30 Sep 2011 11:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-660186</guid>
		<description><![CDATA[most companies don&#039;t want to let one developer know the whole system.  it&#039;s some kind of intellectual protection of the company..]]></description>
		<content:encoded><![CDATA[<p>most companies don&#8217;t want to let one developer know the whole system.  it&#8217;s some kind of intellectual protection of the company..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sanjer</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-660143</link>
		<dc:creator><![CDATA[Sanjer]]></dc:creator>
		<pubDate>Fri, 30 Sep 2011 06:30:31 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-660143</guid>
		<description><![CDATA[Technology is becoming easier day by day in relation to programming. If all the team members share their thoughts at regular intervals during the development surely the outcome will be a humanized solution. This would help many minds pick many minds, understand different behavioural patterns from the developers from the end-user perpspective and match the end-user expectations.

In today&#039;s ever changing,new  frameworks&#039; era, I believe the intelligent person is the one who knows where the information IS not the one who knows it. Generalist are the ones who are specialispts and know where the others know information IS.]]></description>
		<content:encoded><![CDATA[<p>Technology is becoming easier day by day in relation to programming. If all the team members share their thoughts at regular intervals during the development surely the outcome will be a humanized solution. This would help many minds pick many minds, understand different behavioural patterns from the developers from the end-user perpspective and match the end-user expectations.</p>
<p>In today&#8217;s ever changing,new  frameworks&#8217; era, I believe the intelligent person is the one who knows where the information IS not the one who knows it. Generalist are the ones who are specialispts and know where the others know information IS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: walkingthepattern</title>
		<link>http://gigaom.com/2011/09/29/scaling-lessons-from-googles-cio/#comment-660047</link>
		<dc:creator><![CDATA[walkingthepattern]]></dc:creator>
		<pubDate>Thu, 29 Sep 2011 21:55:09 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=413170#comment-660047</guid>
		<description><![CDATA[Are we talking about generalization in relation to the development and workings of any given system, or generalization in terms of skill sets, i.e. a Jack of all trades?

If it&#039;s the former, I&#039;m all for the idea of developers keeping a broader understanding of projects with which they&#039;re involved.  Otherwise, you wind up with a low bus factor, and possibly even a production line-type environment where everyone has an area of the project that they know best.  Neither case is desirable, and having developers that understand how the whole system works is one way to solve the problem.

If it&#039;s the latter, remember how the phrase goes: Jack of all trades, master of none.  Generalization regarding skill sets is good to a certain degree, and developers having to adapt with technology as it changes is nothing new.  But trying to keep up with every new language, framework, and development methodology can lead to slow-moving projects.  People have to specialize sometimes because when time is invested in learning every new technology, the depth of that knowledge can suffer.]]></description>
		<content:encoded><![CDATA[<p>Are we talking about generalization in relation to the development and workings of any given system, or generalization in terms of skill sets, i.e. a Jack of all trades?</p>
<p>If it&#8217;s the former, I&#8217;m all for the idea of developers keeping a broader understanding of projects with which they&#8217;re involved.  Otherwise, you wind up with a low bus factor, and possibly even a production line-type environment where everyone has an area of the project that they know best.  Neither case is desirable, and having developers that understand how the whole system works is one way to solve the problem.</p>
<p>If it&#8217;s the latter, remember how the phrase goes: Jack of all trades, master of none.  Generalization regarding skill sets is good to a certain degree, and developers having to adapt with technology as it changes is nothing new.  But trying to keep up with every new language, framework, and development methodology can lead to slow-moving projects.  People have to specialize sometimes because when time is invested in learning every new technology, the depth of that knowledge can suffer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
