<?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: Does code base structure follow organization structure?</title>
	<atom:link href="http://p.einarsen.no/does-code-base-structure-follow-organization-structure/feed/" rel="self" type="application/rss+xml" />
	<link>http://p.einarsen.no/does-code-base-structure-follow-organization-structure/</link>
	<description></description>
	<lastBuildDate>Thu, 14 Jul 2011 22:53:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Trevor</title>
		<link>http://p.einarsen.no/does-code-base-structure-follow-organization-structure/comment-page-1/#comment-1169</link>
		<dc:creator>Trevor</dc:creator>
		<pubDate>Tue, 02 Mar 2010 11:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://p.einarsen.no/does-code-base-structure-follow-organization-structure/#comment-1169</guid>
		<description>Well, organization and code structure could be similar if the people creating the organization&#039;s hierarchy are also the same kind of people doing the employing, or at least managing the things that determine whether employees stay with the organization or leave. The chances are, though, that at any time there will be a mix of employees at least to some extent trying to reproduce the type of code structure in which they believe.

Whether this would be a good or bad thing, in my opinion, is whether the customer can accept the product. Even though most of the code might be transparent to the customer, when it comes time to talk about new features one might find that a hierarchically structured code lacks the flexibility to match the changing needs of a customer with a more flat structured organization. And vice versa. In terms of business success as a supplier, it might be worth having on board people capable of understanding the essential need in people for hierarchical, or flat, structures so that the code produced does not lock out the other type of structure.</description>
		<content:encoded><![CDATA[<p>Well, organization and code structure could be similar if the people creating the organization&#8217;s hierarchy are also the same kind of people doing the employing, or at least managing the things that determine whether employees stay with the organization or leave. The chances are, though, that at any time there will be a mix of employees at least to some extent trying to reproduce the type of code structure in which they believe.</p>
<p>Whether this would be a good or bad thing, in my opinion, is whether the customer can accept the product. Even though most of the code might be transparent to the customer, when it comes time to talk about new features one might find that a hierarchically structured code lacks the flexibility to match the changing needs of a customer with a more flat structured organization. And vice versa. In terms of business success as a supplier, it might be worth having on board people capable of understanding the essential need in people for hierarchical, or flat, structures so that the code produced does not lock out the other type of structure.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

