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

  
<title>Coding the Architecture - The key difference between developer and architect roles</title>
<link>http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html</link>
<description> At our last user group, we asked people what they thought the key difference between the developer and architect roles was. I said that I&#039;d publish the results, so here they are :        Architect has responsibility for ensuring coherence of all aspects ...</description>
<language>en</language>
<managingEditor>Simon Brown</managingEditor>
<lastBuildDate>Tue, 27 Apr 2010 13:52:42 GMT</lastBuildDate>
  
  

  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Re: The key difference between developer and architect roles</title>
    <link>http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html#comment1275581566730</link>
    <description>
      I on the contrary agree that Morgan&#039;s point is a very (if not the most) important point. I&#039;d say a successful architect&#039;s second biggest asset are soft skills, the first being good awareness of technology and the ability to think strategically and see the bigger picture. It can get very challenging at times to sell one&#039;s ideas and vision to other stakeholders (I&#039;ll refrain from using the M word) even when one can see that those ideas will lead to success. Being able to create consensus and make others feel that they&#039;ve also contributed to the overall idea is critical and not many can do that. That apart, engaging with peers in a constructive manner and getting development teams to think in terms of their contribution to the overall solution is again something an architect with good soft skills can achieve.
    </description>
    <author>Subhashish</author>
    <comments>http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html#comment1275581566730</guid>
    <pubDate>Thu, 03 Jun 2010 16:12:46 GMT</pubDate>
  </item>
  
  <item>
    <title>Re: The key difference between developer and architect roles</title>
    <link>http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html#comment1272376362095</link>
    <description>
      Morgan perhaps you&#039;re getting confused. This article is talking about a &#039;software&#039; architect....
    </description>
    <author>Anonymous</author>
    <comments>http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html#comment1272376362095</guid>
    <pubDate>Tue, 27 Apr 2010 13:52:42 GMT</pubDate>
  </item>
  
  <item>
    <title>Re: The key difference between developer and architect roles</title>
    <link>http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html#comment1213786156456</link>
    <description>
      Architect is a person responsible for performance,scalability and extensibility of an application
    </description>
    <author>Asif Rahim</author>
    <comments>http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2008/02/11/the_key_difference_between_developer_and_architect_roles.html#comment1213786156456</guid>
    <pubDate>Wed, 18 Jun 2008 10:49:16 GMT</pubDate>
  </item>
  
  </channel>
</rss>
