<?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: Two Steps Up, One Step Back</title>
	<atom:link href="http://third-bit.com/blog/archives/3483.html/feed" rel="self" type="application/rss+xml" />
	<link>http://third-bit.com/blog/archives/3483.html</link>
	<description>Data is ones and zeroes &#124; Software is ones and zeroes and hard work.</description>
	<lastBuildDate>Fri, 03 Feb 2012 17:07:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Louis-Philippe Huberdeau</title>
		<link>http://third-bit.com/blog/archives/3483.html#comment-3413</link>
		<dc:creator>Louis-Philippe Huberdeau</dc:creator>
		<pubDate>Mon, 01 Feb 2010 15:25:39 +0000</pubDate>
		<guid isPermaLink="false">http://pyre.third-bit.com/blog/?p=3483#comment-3413</guid>
		<description>How many students per team was that?

I remember having such problems when in university. There were basically two reasons:

1. You always end up with someone too lazy to set-up their development environment correctly and refusing to check-in their code. It breaks the dynamic for everyone else. The cure to this one was to never work with them again.
2. The university did not provide a location for repositories and it had to be figured out every time. We first had to select a location, then a VCS to use. Some students had servers, others had preferences. For small projects, setting up version control took more time than actually doing the project.

This should partially be resolved now with DVCS. You can start locally and simply push to any server where you have shell access, and move around as needed. No need for anything to be installed on the server.

By the time I was out, they did set-up a central location after years of requests.</description>
		<content:encoded><![CDATA[<p>How many students per team was that?</p>
<p>I remember having such problems when in university. There were basically two reasons:</p>
<p>1. You always end up with someone too lazy to set-up their development environment correctly and refusing to check-in their code. It breaks the dynamic for everyone else. The cure to this one was to never work with them again.<br />
2. The university did not provide a location for repositories and it had to be figured out every time. We first had to select a location, then a VCS to use. Some students had servers, others had preferences. For small projects, setting up version control took more time than actually doing the project.</p>
<p>This should partially be resolved now with DVCS. You can start locally and simply push to any server where you have shell access, and move around as needed. No need for anything to be installed on the server.</p>
<p>By the time I was out, they did set-up a central location after years of requests.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

