Thread: New Members
View Single Post
  #3   Spotlight this post!  
Unread 16-09-2013, 13:20
E Dawg E Dawg is offline
... is not done with FRC yet.
AKA: Ethan
FRC #0159 (Alpine Robotics)
Team Role: Mentor
 
Join Date: Feb 2013
Rookie Year: 2012
Location: Fort Collins, CO
Posts: 267
E Dawg has much to be proud ofE Dawg has much to be proud ofE Dawg has much to be proud ofE Dawg has much to be proud ofE Dawg has much to be proud ofE Dawg has much to be proud ofE Dawg has much to be proud ofE Dawg has much to be proud ofE Dawg has much to be proud of
Re: New Members

I would suggest having some of the veteran team members act in a quasi-mentor role some of the time. Of course, they will probably want to work on the robot from time to time (or have to), but on our team this pretty much clears up any problems that may stem from a lack of mentors.

As for the question of students, it really depends on when your team meets. If you meet as a class (during school hours) you will have to restrict the number of people on your team via requirements such as grades, previous technology classes, behavioral records (if that kind of thing concerns you, and other various background information that matters to you. You could also draw out of a hat, but that may seem unfair to some students. If you meet outside of school, there are always ways to accommodate more people. You could do this by breaking people up into ever smaller groups, but I find that this can restrict communications within the team. I would recommend splitting the team up into groups with each meeting on a different day. For example, group A would meet on Monday and Wednesday. Group B would meet Tuesday and Thursday. Everyone would get Friday off. In the end, though, you should stick with what YOU are comfortable with as not everyone's system works for others. The important thing is that you are still furthering the goals of FIRST while still meeting the needs of yourself and others.
Reply With Quote