<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.1" -->
<rss version="0.92">
<channel>
	<title>Changelogic weblog</title>
	<link>http://www.changelogic.com/weblog</link>
	<description>Nonlinearities of software development</description>
	<lastBuildDate>Tue, 03 Oct 2006 19:05:55 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>What you&#8217;ll write tomorrow is not what you think today</title>
		<description>My favourite idea from Extreme Programming is that you should not run your imagination wild and try to conjure future requirements from a chrystal ball. Instead, you should design and write something lightweight that works for current requirements and refactor it later, if needed.

Why have I grown fond of this philosophy? Wouldn't ...</description>
		<link>http://www.changelogic.com/weblog/2006/10/03/what-youll-write-tomorrow-is-not-what-you-think-today/</link>
			</item>
	<item>
		<title>Aim at a developer, shoot the team</title>
		<description>One day, we were discussing some thoughts about defect root cause analysis in our office. "An exception is always a mistake of a programmer," a project manager explained his rule of thumb to me. "An analyst would never prescribe an exception in the specs, now would he?"

As a former tester ...</description>
		<link>http://www.changelogic.com/weblog/2006/09/21/aim-at-a-developer-shoot-the-team/</link>
			</item>
	<item>
		<title>Software risk profiles</title>
		<description>What I’ve been saying so far about refactoring probably looks like this:  Karel Kravik: “What happens if you refactor your software? You devote a lot of resource to it, but its current value remains the same and you’re happy if it still works the same way. So why should ...</description>
		<link>http://www.changelogic.com/weblog/2006/09/01/software-risk-profiles/</link>
			</item>
	<item>
		<title>Agile Manifesto is a journey, not the destination</title>
		<description> We cannot get started without making clear what the Agile Manifesto is. So let’s push that out quickly. Agile Manifesto is a document that states we should prefer:   Individuals and interactions over processes and tools  Working software over comprehensive documentation  Customer collaboration over contract negotiation ...</description>
		<link>http://www.changelogic.com/weblog/2006/08/23/agile-manifesto-is-a-journey-not-the-destination/</link>
			</item>
	<item>
		<title>Is refactoring economically justified?</title>
		<description>Villu Ruusmann, programmer, Changelogic: "Why are we committing these jar files to CVS? This is such a waste! We should keep them in Maven repository."

Karel Kravik, product manager, Changelogic: "Why? How much costs this extra 200KB?"

Villu Ruusmann: "C'mon man, this just isn't elegant solution! It needs serious refactoring."

Karel Kravik, mumbling ...</description>
		<link>http://www.changelogic.com/weblog/2006/08/14/is-refactoring-economically-justified/</link>
			</item>
	<item>
		<title>Software development is risk taking</title>
		<description>With this post I'll open next top level topic - handling uncertainty in software development.

Let me list some risks from an average software development project:

	Will the functionality be useful for our customers? ("user risks")
	Will there be showstopper bugs? Problems with updates? (quality risks)
	Will we hit the due date? Will we ...</description>
		<link>http://www.changelogic.com/weblog/2006/08/07/software-development-is-risk-taking/</link>
			</item>
	<item>
		<title>Changelogic&#8217;s branching model</title>
		<description>In a previous issue we discussed the evolution of branching models, we identified 4 levels of sophistication, but we didn't solve the problems occurring on Level 2.

In this issue we take a look at how Changelogic branching model copes with these problems.

The problems when using the "branch-off on release" model ...</description>
		<link>http://www.changelogic.com/weblog/2006/08/02/changelogics-branching-model/</link>
			</item>
	<item>
		<title>Evolution of branching models</title>
		<description>This article intends to be an introduction to longer series about version control and branching in particular. On the way I also explain why things in Changelogic work like they work.

I'll make a rough classification of project organizations here based on the sophistication of version control usage:

Level 0 - not ...</description>
		<link>http://www.changelogic.com/weblog/2006/07/31/evolution-of-branching-models/</link>
			</item>
	<item>
		<title>Nonlinearities and us</title>
		<description>In this weblog (I just hate the word blog, it somehow associates with Oracle's blob - a data type quite impossible to get from database, so we'll call our weblog) we are going to write about several topics, that probably, but I'm afraid not always, will describe some nonlinearity, asymmetry ...</description>
		<link>http://www.changelogic.com/weblog/2006/07/14/nonlinearities-and-us/</link>
			</item>
</channel>
</rss>
<div id='error'>
			<p class='wpdberror'><strong>WordPress database error:</strong> [Can't open file: 'wp_slim_stats.MYI' (errno: 145)]<br />
			<code>INSERT INTO wp_slim_stats ( `remote_ip`, `language`, `country`, `referer`, `domain`, `searchterms`, `resource`, `platform`, `browser`, `version`, `dt` ) VALUES ( "644595536", "en-us", "us", "", "", "", "/weblog/feed/rss/", "-1", "34", "", "1269044372" )</code></p>
			</div>