<?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: Software Development and the Whiteboard Paradigm</title>
	<atom:link href="http://sebastien-arbogast.com/2009/09/24/software-development-and-the-whiteboard-paradigm/feed/" rel="self" type="application/rss+xml" />
	<link>http://sebastien-arbogast.com/2009/09/24/software-development-and-the-whiteboard-paradigm/</link>
	<description>Solving Software Problems since 2010</description>
	<lastBuildDate>Thu, 17 May 2012 15:07:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Sébastien</title>
		<link>http://sebastien-arbogast.com/2009/09/24/software-development-and-the-whiteboard-paradigm/comment-page-1/#comment-1119</link>
		<dc:creator>Sébastien</dc:creator>
		<pubDate>Fri, 02 Oct 2009 14:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://sebastien-arbogast.com/?p=280#comment-1119</guid>
		<description>Totally! But now I&#039;m reading about operational transformation and it seems really powerful. When you think about it, common version control systems, the hearts of our collaborative development efforts, work with diffs. They have one version of a text file, you give them another version, it does a diff and stores it in the DB. It&#039;s a simple solution but a wrong one, that poses problems with merging. With OT, what you store is operations themselves, not their results, and transformations guarantee no conflicts. Brilliant. I think I&#039;m gonna do that first: a version control system based on waves... but working directly with abstract structures instead of their text representation... Mmmh...</description>
		<content:encoded><![CDATA[<p>Totally! But now I&#8217;m reading about operational transformation and it seems really powerful. When you think about it, common version control systems, the hearts of our collaborative development efforts, work with diffs. They have one version of a text file, you give them another version, it does a diff and stores it in the DB. It&#8217;s a simple solution but a wrong one, that poses problems with merging. With OT, what you store is operations themselves, not their results, and transformations guarantee no conflicts. Brilliant. I think I&#8217;m gonna do that first: a version control system based on waves&#8230; but working directly with abstract structures instead of their text representation&#8230; Mmmh&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastien Plisson</title>
		<link>http://sebastien-arbogast.com/2009/09/24/software-development-and-the-whiteboard-paradigm/comment-page-1/#comment-1109</link>
		<dc:creator>Sebastien Plisson</dc:creator>
		<pubDate>Thu, 24 Sep 2009 20:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://sebastien-arbogast.com/?p=280#comment-1109</guid>
		<description>Very interesting indeed.
Here are the ideas that it gives me:

Imagine some Google Wave robots that would allow to collaboratively compile the code you contribute inside a wave. The result of this compilation would then generate  a new/update a module-robot/widget that would be deployed on the wave server and be available to others applications and services.

Would not that be great ?</description>
		<content:encoded><![CDATA[<p>Very interesting indeed.<br />
Here are the ideas that it gives me:</p>
<p>Imagine some Google Wave robots that would allow to collaboratively compile the code you contribute inside a wave. The result of this compilation would then generate  a new/update a module-robot/widget that would be deployed on the wave server and be available to others applications and services.</p>
<p>Would not that be great ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

