<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Coding the Architecture - mentoring tag</title>
  <link>http://www.codingthearchitecture.com/tags/mentoring/</link>
  <description>Software architecture for developers</description>
  <language>en</language>
  <copyright>Coding the Architecture</copyright>
  <lastBuildDate>Wed, 16 May 2012 08:01:04 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>The Four Stages of Learning</title>
    <link>http://www.codingthearchitecture.com/2008/03/25/the_four_stages_of_learning.html</link>
    
      
      
        <description>
          &lt;p&gt;
I&#039;ve found many parallels with the four stages of learning in software development, from how a developer&#039;s approach to design changes to how agile teams eventually become self-organising (eg, Scrum&#039;s &#034;readiness levels&#034;). By understanding where someone is on their path to becoming truly good at something you can be more effective in mentoring them to the next level - rather than assuming you can fast-track them right to the top.
&lt;/p&gt;&lt;p&gt;&lt;a href=&#034;http://www.codingthearchitecture.com/2008/03/25/the_four_stages_of_learning.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <category>What is the the role of a software architect?</category>
    
    <comments>http://www.codingthearchitecture.com/2008/03/25/the_four_stages_of_learning.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2008/03/25/the_four_stages_of_learning.html</guid>
    <pubDate>Tue, 25 Mar 2008 10:07:57 GMT</pubDate>
  </item>
  
  </channel>
</rss>

