<?xml version="1.0"?>
<rss version="2.0">
<channel>

  
<title>Coding the Architecture - Architects are part of the team</title>
<link>http://www.codingthearchitecture.com/2006/04/06/architects_are_part_of_the_team.html</link>
<description> One of the problems associated with architects and architecture is the ivory tower syndrome, where others on the team think that an architect is there to dictate from afar, forcing the team to adopt unrealistic principles and designs. In Should ...</description>
<language>en</language>
<managingEditor>Simon Brown</managingEditor>
<lastBuildDate>Sat, 08 Apr 2006 18:12:13 GMT</lastBuildDate>
  
  

  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Making architects are part of the team</title>
    <link>http://www.codingthearchitecture.com/2006/04/06/architects_are_part_of_the_team.html#trackback1144519933960</link>
    <description>
      If you&#039;ve worked in any normal software development shop that has some sort of hierarchy, you know that many times...
    </description>
    <author>106 Miles to Chicago</author>
    <comments>http://www.codingthearchitecture.com/2006/04/06/architects_are_part_of_the_team.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/04/06/architects_are_part_of_the_team.html#trackback1144519933960</guid>
    <pubDate>Sat, 08 Apr 2006 18:12:13 GMT</pubDate>
  </item>
  
  </channel>
</rss>
