﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on How to grow a development team?</title><description>@Adi,
  
2Kg hammer and speak louder j/k
  
</description><link>http://ayende.com/2188/how-to-grow-a-development-team#comment5</link><guid>http://ayende.com/2188/how-to-grow-a-development-team#comment5</guid><pubDate>Fri, 09 Mar 2007 19:29:18 GMT</pubDate></item><item><title>Adi commented on How to grow a development team?</title><description>"Failing all of that, starting to carry a 5Kg hammer and speaking softly always worked for me".
  
Hey, you are a big fellow, what should someone shorter do? :)
</description><link>http://ayende.com/2188/how-to-grow-a-development-team#comment4</link><guid>http://ayende.com/2188/how-to-grow-a-development-team#comment4</guid><pubDate>Fri, 09 Mar 2007 19:20:55 GMT</pubDate></item><item><title>Bill Pierce commented on How to grow a development team?</title><description>@Ayende:
  
"...go look for someone that you really admire, and then convince them to come work as the team leader /architect." 
  
How do you feel about moving to Colorado?
  
  
"I don't want to stand up and spend 30 minutes giving a presentation on IoC and separation of concerns."
  
This came out wrong.  I have no problem talking about new concepts and educating the team and listening to my team educate me.  I just feel that in my situation this is the wrong approach to start off with.  I don't want my teammates to view the code review sessions as 30 minutes of listening to Bill the All Knowing Code Sage explain to them how they can write their code better.  I'd like to use code review as a means to slowly coach the team in the right direction before I hit them with the real gems.  
  
  
  
</description><link>http://ayende.com/2188/how-to-grow-a-development-team#comment3</link><guid>http://ayende.com/2188/how-to-grow-a-development-team#comment3</guid><pubDate>Fri, 09 Mar 2007 15:20:14 GMT</pubDate></item><item><title>Ayende Rahien commented on How to grow a development team?</title><description>I was thinking about it from the other side.
  
It can be frustrating to keep having to educate people around you, when you just want to work. And there are people who will actively resist learning new stuff.
</description><link>http://ayende.com/2188/how-to-grow-a-development-team#comment2</link><guid>http://ayende.com/2188/how-to-grow-a-development-team#comment2</guid><pubDate>Fri, 09 Mar 2007 09:06:20 GMT</pubDate></item><item><title>Darius Damalakas commented on How to grow a development team?</title><description>"Bill, you are really serious about that, get another job. "
  
Very true.
  
  
I say the same - if you don't care for your team mates, don't want to educate them if have the necessary skills, then you are more of a hindrace, than helping the team do the job.  
  
It's definetely not the quality of the team leader to not educate the team.
</description><link>http://ayende.com/2188/how-to-grow-a-development-team#comment1</link><guid>http://ayende.com/2188/how-to-grow-a-development-team#comment1</guid><pubDate>Fri, 09 Mar 2007 07:39:28 GMT</pubDate></item></channel></rss>