<?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: A Glimpse Into How Google Codes</title>
	<atom:link href="http://battellemedia.com/archives/2005/03/a_glimpse_into_how_google_codes.php/feed" rel="self" type="application/rss+xml" />
	<link>http://battellemedia.com/archives/2005/03/a_glimpse_into_how_google_codes.php?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=a_glimpse_into_how_google_codes</link>
	<description>Thoughts on the intersection of search, media, technology, and more.</description>
	<lastBuildDate>Thu, 23 May 2013 12:55:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: av</title>
		<link>http://battellemedia.com/archives/2005/03/a_glimpse_into_how_google_codes.php#comment-21318</link>
		<dc:creator>av</dc:creator>
		<pubDate>Fri, 25 Mar 2005 18:14:36 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2005/03/a_glimpse_into_how_google_codes.php#comment-21318</guid>
		<description>&lt;p&gt;&lt;br /&gt;
Sometimes there is too much hype around the drips that come out as google information. Every reasonably large company tries to keep libraries for  language support, string manipulation etc. Most companies go for divided codelins when they have products that are completely unrelated to each other or things inherited in an acquisition.&lt;/p&gt;

&lt;p&gt;For example, it would be interesting if the blogging, photo sharing and all other services do use the same codebase. I think not.&lt;/p&gt;

&lt;p&gt;Too many of these posts look like PR filtered posts. Tommorow, google will say that we use a source code control system and the blogosphere will lap it up!&lt;/p&gt;

&lt;p&gt;-av&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>
Sometimes there is too much hype around the drips that come out as google information. Every reasonably large company tries to keep libraries for  language support, string manipulation etc. Most companies go for divided codelins when they have products that are completely unrelated to each other or things inherited in an acquisition.</p>
<p>For example, it would be interesting if the blogging, photo sharing and all other services do use the same codebase. I think not.</p>
<p>Too many of these posts look like PR filtered posts. Tommorow, google will say that we use a source code control system and the blogosphere will lap it up!</p>
<p>-av</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabe</title>
		<link>http://battellemedia.com/archives/2005/03/a_glimpse_into_how_google_codes.php#comment-21317</link>
		<dc:creator>Gabe</dc:creator>
		<pubDate>Fri, 25 Mar 2005 17:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2005/03/a_glimpse_into_how_google_codes.php#comment-21317</guid>
		<description>&lt;p&gt;&quot;Most obvious is that it is really easy to look at and contribute to code in other projects without having to talk to anyone, get special permissions or fill out forms in triplicate.&quot;&lt;/p&gt;

&lt;p&gt;For this very reason, I bet corporate spies have already shipped the codebase to China.  (Although replicating Google certainly requires more than just a codebase...)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>&#8220;Most obvious is that it is really easy to look at and contribute to code in other projects without having to talk to anyone, get special permissions or fill out forms in triplicate.&#8221;</p>
<p>For this very reason, I bet corporate spies have already shipped the codebase to China.  (Although replicating Google certainly requires more than just a codebase&#8230;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
