<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Lóránd Somogyi &#187; software architecture</title>
	<atom:link href="http://lorands.com/category/software-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://lorands.com</link>
	<description>Thoughts on Software Development…</description>
	<lastBuildDate>Tue, 16 Aug 2011 08:41:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Why you should Open Source your software?</title>
		<link>http://lorands.com/2008/04/why-should-you-open-source-your-software/</link>
		<comments>http://lorands.com/2008/04/why-should-you-open-source-your-software/#comments</comments>
		<pubDate>Fri, 18 Apr 2008 15:54:21 +0000</pubDate>
		<dc:creator>Lóránd Somogyi</dc:creator>
				<category><![CDATA[FLOSS]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[oss]]></category>
		<category><![CDATA[software architecture]]></category>
		<category><![CDATA[software design]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://lorand.somogyi.name/?p=24</guid>
		<description><![CDATA[Lots of software companies does not Open Source their software. It is a bad practice, and a waste of money. Open Souring your software has a real good ROI. This article is first of all for business people leading software companies, or for those who pay for software development. Actually for all those who are [...]]]></description>
		<wfw:commentRss>http://lorands.com/2008/04/why-should-you-open-source-your-software/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Continuum 1.1 with LDAP and the Roles hack</title>
		<link>http://lorands.com/2008/03/continuum-11-with-ldap-and-the-roles-hack/</link>
		<comments>http://lorands.com/2008/03/continuum-11-with-ldap-and-the-roles-hack/#comments</comments>
		<pubDate>Fri, 21 Mar 2008 12:53:48 +0000</pubDate>
		<dc:creator>Lóránd Somogyi</dc:creator>
				<category><![CDATA[ci]]></category>
		<category><![CDATA[continuum]]></category>
		<category><![CDATA[ldap]]></category>
		<category><![CDATA[software architecture]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://lorand.somogyi.name/index.php/2008/03/21/continuum-11-with-ldap-and-the-roles-hack/</guid>
		<description><![CDATA[We use Continuum 1.1 as our Continuous Integration server. We also have an LDAP directory that we like to use whenever it comes to user management. So we tried to integrate Continuum with LDAP. As described by the documentation, and here we configured the Continuum to use LDAP authentication. Everything looked fine. Users could log [...]]]></description>
		<wfw:commentRss>http://lorands.com/2008/03/continuum-11-with-ldap-and-the-roles-hack/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Plan, plan, plan part II: What you don&#8217;t need</title>
		<link>http://lorands.com/2008/03/plan-plan-plan-part-ii-what-you-dont-need/</link>
		<comments>http://lorands.com/2008/03/plan-plan-plan-part-ii-what-you-dont-need/#comments</comments>
		<pubDate>Mon, 17 Mar 2008 20:29:12 +0000</pubDate>
		<dc:creator>Lóránd Somogyi</dc:creator>
				<category><![CDATA[software architecture]]></category>
		<category><![CDATA[software design]]></category>

		<guid isPermaLink="false">http://lorand.somogyi.name/index.php/2008/03/17/plan-plan-plan-part-ii-what-you-dont-need/</guid>
		<description><![CDATA[This is the next article on planning, and what could go wrong on a huge project, and what to do to avoid pitfalls. The first part was about technical feature planning. Here, I&#8217;m about to write a bit about the very start of the project, the first plan and vision, and what you want to [...]]]></description>
		<wfw:commentRss>http://lorands.com/2008/03/plan-plan-plan-part-ii-what-you-dont-need/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Plan, plan, plan&#8230;</title>
		<link>http://lorands.com/2008/03/plan-plan-plan/</link>
		<comments>http://lorands.com/2008/03/plan-plan-plan/#comments</comments>
		<pubDate>Wed, 12 Mar 2008 21:28:39 +0000</pubDate>
		<dc:creator>Lóránd Somogyi</dc:creator>
				<category><![CDATA[software architecture]]></category>
		<category><![CDATA[software design]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://lorand.somogyi.name/index.php/2008/03/12/plan-plan-plan/</guid>
		<description><![CDATA[Working on a huge legacy system as a software architect, the most valuable lesson learned is: plan, plan, plan and do it as soon as you can Beside of normal design planning, resource planning and stuff you might think of, there is different aspect of planning. I call it &#8220;technical feature planning&#8221;. It might be [...]]]></description>
		<wfw:commentRss>http://lorands.com/2008/03/plan-plan-plan/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

