The Meaning of FIRST

[Akash Rastogi]

Originally Posted by JM033

If there is a team of 10 students and none want to program or have interest in programming, should this team not use other resources in order to have the most successful robot possible?

No, they already have enough adequate resources. Coming from a team with 2 programmers, I believe even 4 programmers is a fair amount. Why would one like to join the programming subteam if they didn't even have any interest? If you need more resources because you are unable to provide ANYTHING yourself, it's just pure laziness and unwillingness then. You wouldn't learn anything if you had others do your work for you. This team had adequate amount of programmers, but seemed to fail to use them for the "success of a great bot".

J and OP, you don't know the full story.

Mentoring is HARD. Even if you come from being on an FRC team in high school and then mentor, it is incredibly hard for any mentor to judge and gauge when and where they need to step in to get something done.

I personally no longer care who does what on a team because it is not my place to judge. I used to say the same things as you until I started mentoring. Don't be so quick to judge, once you (if you do) begin to mentor a team, you will also learn how difficult a task it is to know when to step in and when you need to let students or some aspect of the robot fail in order to teach the students.

With that said, I always dislike these threads because people don't fully think things through before making the thread. It is always easy to quickly get upset about a perceived situation, but take the time to think things out before judging a team.

[spikeman62]

I think the argument you are making is just based on too small of a sample size. This point has been made, but there are over 2500 teams in FIRST, they all aren't going to run how you want. That's just not how FIRST works. There are many different ways to "skin the cat" that is, building a robot and more importantly, inspiring students. And believe me when I say that many teams do not have the adequate resources to have depth at every level of the engineering process.

On my team until recently, we were lucky to have 10 kids on the team. And really only about five of those were dedicated and came almost every day. Many of us didn't have a engineering background so we needed our mentors to step up and teach us what we didn't know. Yes that meant sometimes they had to machine a part or do some of the coding but that didn't mean we were incapable or that they weren't letting us do anything, they just had the experience. We did our fair share of the work and the mentors did theirs. The combination of the two is what gets the robot done in six weeks. I can honestly say that without my mentors, I wouldn't be where I am today or have the knowledge of engineering that I have. They have taught me so many lessons, not just about robots, but about life. They have truly inspired me.

I can tell you the high majority of mentors are there for the greater good to inspire and teach you. I think you're letting one mentor skew your entire image of what a mentor truly is.

[faust1706]

FIRST for me is getting to opportunity to learn from the smartest people I know, the mentors. They made it a point this year to be hands off on design, build, and programming. Our teacher sponsor and a team member's mom assembled our bumpers this year. The students got all the material and cut the wood, they assembled it. Anyways, a mentor I worked very close with is an engineer at Boeing. He showed me the ropes of programming last year, and told me to have at it. This year was a little more structured, he knew where the program needed to go, told me, and I had to figure out how to get it there. I feel this was a great system for learning, because if I ever had an questions concerning my programming logic, we would take to the whiteboard, where anyone was welcome to try and point out flaws with us. He's done more for me that taught me how to program a Kinect. He's INSPIRED me to learn programming on my own. If it weren't for him, I wouldn't be asking why and how, I'd be playing LoL. Now, I do both XD

[Tungrus]

In our team students do most of the things. Mentors do purchasing, scheduling and paper work and software setup on laptop/netbook. Students come up with design, have sub-teams review with mentor and other sub-team. Discuss alternate approach, decide on what we can do in 6 weeks, decide on nice to have features. Get to work, fabricate and assemble, we have basic tools, does not require much training. When mentor sees something may not work, he will gather the team discuss the potential problem and guide in possible solution. If he has no answer, we sleep on it for a later day. Our aim is not to win and go to championship, if we can design and build something is ready to compete, we will be proud. We win some matches and lose some...its life. When we get award, we thank judges for recognizing our efforts. We too come from FLL background our mentors then guided us to do everything, the followed FLL by book. No complaints. This is who we are.

[connor.worley]

To quote JVN at a workshop, "There are years when I've designed the entire robot, and years when I've never touched the CAD mouse. It all depends on what the students are capable of, and how far they want to take their skills." (probably some exaggeration here, but you get the point). Our team has two people who can write code, one being me and the other being a mentor. Outside of competition, the programming work is a joint effort, but during competition, I work in the stands to help with scouting. This means that during competition, all programming changes are made by our mentor. This does not reflect who does what amount of work throughout the entire season, but works best for our team. Make sure to understand a team's situation before you make assumptions about them.

Another platitude: a mentor should be a coworker, not a help desk.