<?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: Das Hanselman wants a piece of this!</title>
	<atom:link href="http://www.ronaldwidha.net/2010/02/21/das-hanselman-wants-a-piece-of-this/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ronaldwidha.net/2010/02/21/das-hanselman-wants-a-piece-of-this/</link>
	<description>podcast addict, believes in occam razor, software consultant</description>
	<lastBuildDate>Thu, 02 Feb 2012 23:00:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: wilslm</title>
		<link>http://www.ronaldwidha.net/2010/02/21/das-hanselman-wants-a-piece-of-this/comment-page-1/#comment-440</link>
		<dc:creator>wilslm</dc:creator>
		<pubDate>Sun, 21 Feb 2010 18:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.ronaldwidha.net/2010/02/21/das-hanselman-wants-a-piece-of-this/#comment-440</guid>
		<description>Hey Ronald,&lt;br&gt;&lt;br&gt;In the last 4 years I have been working with many solution architects. It is interesting to see many of them have totally different skill sets ranges from documentation person ONLY; mainly writing technical design documentation to someone who can go to low level implementation i.e coding. &lt;br&gt;&lt;br&gt;Typically in a big organisation, an architect only knows everything at the high level because their daily tools are Microsoft PowerPoint and Word not C#,Python, or Java. They are mainly there to be the bridge between Business Analysts and Developers. Hence it is not uncommon to see that later during the development stage, the architect will come back and say that one of the requirements cannot be implemented or the time frame is not sufficient. Simply they have no idea of the effort required. &lt;br&gt;&lt;br&gt;Personally I would prefer to have an architect that has low level technical skills, the best candidate for this is obviously a Senior Developer. He/She can design a solution and write a documentation that make sense and practical enough to the junior developers to develop. &lt;br&gt;&lt;br&gt;Having said that I would argue it would be extremely difficult to find a Senior Developer who has a wide range of technical skills. Remember building a solution involves multiple components, a typical Software Developer has often had a limited skill set.</description>
		<content:encoded><![CDATA[<p>Hey Ronald,</p>
<p>In the last 4 years I have been working with many solution architects. It is interesting to see many of them have totally different skill sets ranges from documentation person ONLY; mainly writing technical design documentation to someone who can go to low level implementation i.e coding. </p>
<p>Typically in a big organisation, an architect only knows everything at the high level because their daily tools are Microsoft PowerPoint and Word not C#,Python, or Java. They are mainly there to be the bridge between Business Analysts and Developers. Hence it is not uncommon to see that later during the development stage, the architect will come back and say that one of the requirements cannot be implemented or the time frame is not sufficient. Simply they have no idea of the effort required. </p>
<p>Personally I would prefer to have an architect that has low level technical skills, the best candidate for this is obviously a Senior Developer. He/She can design a solution and write a documentation that make sense and practical enough to the junior developers to develop. </p>
<p>Having said that I would argue it would be extremely difficult to find a Senior Developer who has a wide range of technical skills. Remember building a solution involves multiple components, a typical Software Developer has often had a limited skill set.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

