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

  
<title>Coding the Architecture - Contract architects</title>
<link>http://www.codingthearchitecture.com/2007/01/12/contract_architects.html</link>
<description> So, we were in the pub this evening and the subject of contracting (i.e. going independent) came up. Without a doubt, we all agreed the contract market is awash with roles that are focussed on software development. Lots of companies are willing to ...</description>
<language>en</language>
<managingEditor>Simon Brown</managingEditor>
<lastBuildDate>Mon, 15 Jan 2007 15:52:35 GMT</lastBuildDate>
  
  

  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Re: Contract architects</title>
    <link>http://www.codingthearchitecture.com/2007/01/12/contract_architects.html#comment1170264527147</link>
    <description>
      &lt;p&gt;As well as trust, there is perhaps also a bit more safety in using a consultant. In theory, the consultancy is offering a guarantee of the consultant&#039;s skills and can replace them should they prove unsuitable or if they stop being available. This also gives greater continuity when people are moving between companies/roles/contracts.&lt;/p&gt;
&lt;p&gt;Outside the world of discrete software products, technical architecture may also be regarded as an ongoing role (unlike in the building industry), and is slightly less suited to the contractor/consultant market where it could be costly if undertaken by retainer without a continual stream of projects.&lt;/p&gt;
&lt;p&gt;No doubt there are examples of where businesses have processes in place to prevent islands of knowledge forming and can work successfully with permies, consultants and contractors alike.&lt;/p&gt;
    </description>
    <author>Kevin Seal</author>
    <comments>http://www.codingthearchitecture.com/2007/01/12/contract_architects.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2007/01/12/contract_architects.html#comment1170264527147</guid>
    <pubDate>Wed, 31 Jan 2007 17:28:47 GMT</pubDate>
  </item>
  
  <item>
    <title>Re: Contract architects</title>
    <link>http://www.codingthearchitecture.com/2007/01/12/contract_architects.html#comment1168964588313</link>
    <description>
      As a contract technical architect I can vouch for Alex&#039;s comment.&lt;br /&gt;
&lt;br /&gt;
I can also confirm that if the management believed that they would be more comfortable if I was permie then they would be wrong ;)&lt;br /&gt;
&lt;br /&gt;
Matt.
    </description>
    <author>Matt Read</author>
    <comments>http://www.codingthearchitecture.com/2007/01/12/contract_architects.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2007/01/12/contract_architects.html#comment1168964588313</guid>
    <pubDate>Tue, 16 Jan 2007 16:23:08 GMT</pubDate>
  </item>
  
  <item>
    <title>Re: Contract architects</title>
    <link>http://www.codingthearchitecture.com/2007/01/12/contract_architects.html#comment1168938164334</link>
    <description>
      Job title inflation is definitely a whole topic in it&#039;s own right..&lt;br /&gt;
&lt;br /&gt;
I would think that there is more job title inflation for permanent roles that there is for contract roles.&amp;nbsp; Permanent people tend to buy in more to prestige/status than contractors, well at least the ones I know do.
    </description>
    <author>Dave Allison</author>
    <comments>http://www.codingthearchitecture.com/2007/01/12/contract_architects.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2007/01/12/contract_architects.html#comment1168938164334</guid>
    <pubDate>Tue, 16 Jan 2007 09:02:44 GMT</pubDate>
  </item>
  
  </channel>
</rss>
