<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Coding the Architecture - pitfalls tag</title>
  <link>http://www.codingthearchitecture.com/tags/pitfalls/</link>
  <description>Software architecture for developers</description>
  <language>en</language>
  <copyright>Coding the Architecture</copyright>
  <lastBuildDate>Mon, 21 May 2012 09:41:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Pitfalls for software architects</title>
    <link>http://www.codingthearchitecture.com/2009/03/30/pitfalls_for_software_architects.html</link>
    
      
        <description>
          &lt;p&gt;
Thanks to everybody that came along to my &#034;Pitfalls for new software architects&#034; talk at DevWeek 2009 last week ... I hope you found it a useful look at some of the traps that I&#039;ve seen people (including myself!) fall into over the years. The pitfalls are structured into a number of different areas as shown in the diagram below.
&lt;/p&gt;

&lt;div align=&#034;center&#034;&gt;
&lt;img src=&#034;http://www.codingthearchitecture.com/images/book/role-1.png&#034; alt=&#034;Role of a hands-on software architect&#034; /&gt;
&lt;/div&gt;

&lt;p&gt;
Each of these areas is part of our view of &lt;a href=&#034;http://www.codingthearchitecture.com/pages/book/role.html&#034;&gt;what a hands-on software architect should do&lt;/a&gt;, and the talk itself compliments a session I delivered at Software Architect 2008 called &#034;Why software projects fail&#034;. You can download the slides for both sessions below.
&lt;/p&gt;

&lt;div align=&#034;center&#034;&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/dw2009-pitfalls-for-new-software-architects.pdf&#034;&gt;&lt;img src=&#034;http://www.codingthearchitecture.com/images/dw2009-pfnsa-thumbnails.png&#034; alt=&#034;Pitfalls for new software architects&#034; border=&#034;0&#034; /&gt;&lt;/a&gt;
&lt;br/&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/dw2009-pitfalls-for-new-software-architects.pdf&#034;&gt;Pitfalls for new software architects&lt;/a&gt; (PDF, ~4MB)
&lt;br /&gt;&lt;br /&gt;
&lt;/div&gt;

&lt;div align=&#034;center&#034;&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/sa2008-why-software-projects-fail.pdf&#034;&gt;&lt;img src=&#034;http://www.codingthearchitecture.com/images/sa2008-wspf-thumbnails.png&#034; alt=&#034;Why software projects fail&#034; border=&#034;0&#034; /&gt;&lt;/a&gt;
&lt;br/&gt;
&lt;a href=&#034;http://static.codingthearchitecture.com/presentations/sa2008-why-software-projects-fail.pdf&#034;&gt;Why software projects fail&lt;/a&gt; (PDF, ~6MB)
&lt;/div&gt;
        </description>
      
      
    
    
    
    <comments>http://www.codingthearchitecture.com/2009/03/30/pitfalls_for_software_architects.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2009/03/30/pitfalls_for_software_architects.html</guid>
    <pubDate>Mon, 30 Mar 2009 08:50:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>

