View Single Post
  #20   Spotlight this post!  
Unread 06-01-2017, 10:28
GreyingJay GreyingJay is online now
Robonut
AKA: Mr. Lam
FRC #2706 (Merge Robotics)
Team Role: Mentor
 
Join Date: Mar 2015
Rookie Year: 2015
Location: Ottawa, Canada
Posts: 778
GreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond reputeGreyingJay has a reputation beyond repute
Re: Mentoring New Team

I've got good news and bad news:

Based on my experience, building the actual robot is the least of your worries.

That was both the good news and the bad news.

Last year was 2706's first year as a new, veteran team (spun off from another local team). Being involved in the team administration for the first time was eye-opening, as there is a LOT of stuff going on:
- team registrations (tracking your own paperwork, waivers, and also STIMS/TIMS)
- competition transportation and lodging logistics
- getting a leadership structure in place for your mentors and students
- setting up subteams
- finding sponsors
- planning fundraising events
- planning and ordering parts
- answering the many emails you'll start getting from... everyone
- teaching students the skills they need: hardware, software, communications, planning, conflict resolution, etc.
- team building
- team branding and marketing (shirts, banners, logos, pit)
- awards

You'll note the robot itself is not on that list anywhere.

So this is good news because your mentors don't need to be robotics experts. Experience in any sort of school/club/Scouts/Guides/camp/team environment is directly applicable. I'm a software guy, but when I started doing FRC I was learning everything directly alongside the students. I was maybe a half-step ahead of them thanks to my industry experience. And that's OK. I think that was a great way to learn, and it models to the students how to go and get the answers they need.

As for the robot itself, as you'll see from 1114 and everywhere else: Simple, simple, simple. Build the kitbot. Nice thing is that this doesn't require dedicated shop tools or all that much specialized knowledge. Then expand on it according to your skill and equipment. Build something that's reliable, that does whatever it does consistently.

As Karthik says, find something simple to do in the game that's within your reach, and be damned good at it. Practice the heck out of it. The nice thing about this strategy is it doesn't require a fancy robot, and therefore, fancy fabrication or programming skills from your mentors. A willingness to learn is all it takes. And, realistically, the ability to sell the "simple" concept to your students, because everyone will be tempted to try to take on more. You have to know to stop before you've taken on too much.

Good luck!
__________________
"If I'm going to mentor someone, I'm going to be involved in their life as a positive force." -Mechvet

Last edited by GreyingJay : 06-01-2017 at 10:31.
Reply With Quote