View Single Post
  #12   Spotlight this post!  
Unread 02-03-2012, 08:20
dbeckwith's Avatar
dbeckwith dbeckwith is offline
Lead Programmer
AKA: Daniel Beckwith
FRC #3205 (The Patriots)
Team Role: Programmer
 
Join Date: Jan 2010
Rookie Year: 2009
Location: USA
Posts: 84
dbeckwith is an unknown quantity at this point
Re: Challenges of small teams with fewer than 10 students

Quote:
Originally Posted by MAldridge View Post
I have the unique perspective of having just moved from a small team (~7 people) in one state, to a large team (~35 people) in another state. In the small team, everyone did everything, but we usually had to rely on only about 3 people with the specialized skills such as programming and electrical engineering.

On the larger team, I find that as a programmer, I can be far more specialized and get more done. I can easily just say that I need something added or adjusted on the robot and it gets done. It's easy to concentrate more on what I need to get done, and since I really like programming, I prefer this arrangement.
On our small team (~10) it's a little different. As metainf said, we (team 3205) have about 4 or 5 people who know everything and organize everything, and all the new members just kind of tag along and try to learn stuff but don't help very much. As a result our progress is usually slow but honestly I think I would prefer this to a larger team because everyone at least gets a chance to contribute and everyone gets to work on every part of the robot. I feel like on our team we get a more hands-on experience and a more meaningful attachment to our robot. Larger teams may be more efficient, but I think you lose that personal connection with the robot that everyone gets on a small team.
__________________
q = (2*b) | ~(2*b);

if (life.getLemons() != null) this.lemonade = new Drink(life.getLemons());
else throw new NoLemonsException("What now?");


Reply With Quote