New to robotics...feel lost, useless, and robotics career question

[EricH]

Originally Posted by Bharat Nain

If I had to pick something I'd say scouting. Are there any kids on your team who are good scouts? Then you can sit and research teams and at competitions you know what to do and who to talk to. Tip: The history of teams plays a major role in their performance every year.

Scouting is probably the number one most overlooked area in FIRST. I hav actually seen two teams at the same event who did not do their scouting have to borrow a sheet from another team. Don't be one of those teams who says, "Aw, we'll never make it to the eliminations, we don't need scouting," and is caught unprepared when someone else thinks they are the best team around and neither team has a scouting sheet. Find or make a sheet that you can use and train at least one or two others (preferably the whole team) in the use of it. Try the Scouting Forum or Whitepapers for examples.

[Justin Montois]

Don't give up on it yet. Robotics, especially in FIRST is an amazing program. When some people first start out they feel outside the group and feel like they have nothing to do but over time you will find you niche, and when you do take it as far as it can go. You will learn to love this program, I am sure of it.

[Mullen]

what ever you do, DO NOT give up. i promise you it will get better. my first year i didnt really know all that much about robotics, in fact..i pretty much didnt know anything. but my brother had left his legacy for the team and everyone had high expectations. so my first year i just jumped from group to group and tried to get my hands on a little bit of everything, to see what i liked the most and, 5 years later, im still helping out.

so even though now you may feel lost and useless, just jump in there and get your hands dirty, the more effort you show the more responsibilities and respect you'll recieve

[KenWittlief]

Originally Posted by EricH

Scouting is probably the number one most overlooked area in FIRST. .

scouting is important at the events

but Legola52 needs to find his nitch on the team now. The 1st regional is still a long way off.

we had a guy on our team a few years back whos older sister had been on the team for three years. He had been to regionals, and to the championship at Epcot with the family.

His first year on the team he thought he knew what FIRST was all about, and all about the robot design and fabrication. But he kinda floated around and didnt really click with anything in particular.

When we got the kit of parts after the kickoff, I asked him to check out the pneumatics, to check all the cylinders and the compressor and valves, and to make sure all the parts worked.

He charged up a tank and connected the biggest cylinder, with a valve and some hosing, and manually triggered the valve, switching the cylinder back and forth at full pressure.

he got this look in his eye (and I had the feeling we were in trouble :^). That year he lead the pnuematics design and implementation on the robot.

You never know whats going to grab your imagination when you are on a FIRST team.

[SirLancelot]

I agree with all of the above--pick a field and you may learn to love it!!

There's never a shortage of things to do, and not all of them are obscure. You could learn the 'C' programming language (I suggest the tutorials at cplus.about.com, by the way), you could teach yourself Inventor, or you could simply find a mentor and aquaint yourself with some of the power tools and become one of the team's machinists.
If your team hasn't already done so, you may wish to consider sketching out your robot idea for this season and delegating each person to a specific aspect of it based on personal interest. That way, each person will have a job that they'll (hopefully) enjoy, and they'll learn a lot about it in the process.
1502 was a rookie team last year, and I'm know well the feeling of being useless. I just decided to teach myself Inventor, and after that, the bad feelings were gone. I know that I'm needed for something that no one else on our team is yet capable of doing. If you find a purpose for being there, FIRST is a blast. Everything will get better!!

best of luck to you and your team!
~Anna

[EricH]

Originally Posted by KenWittlief

scouting is important at the events

but Legola52 needs to find his nitch on the team now. The 1st regional is still a long way off.

Scouting needs proper prep work. I had a sheet 3/4 finished by the end of Week 1.
If no one else is thinking about weight, someone should. Legolas52, that could be you or someone else, but weight is very important. You need to know how much the robot weighs (as closely as you can) so you know how many holes to drill or what parts to remove if you are overweight. If you are over 120 pounds without the battery and/or bumpers, you will not compete.

[Kim Masi]

my first year of FIRST was quite challenging. I think everyone feels a little lost their first year because they don't know what they can contribute to the team. for someone like me, who had no engineering or mechanical or even computer skills whatsoever who just thought robotics sounded interesting, and i am now one of the leaders of the team, i was the driver last year and now im helping with the fabrication of parts and learning how to use the machines.

my first year i designed the tee-shirts and did public relations and video. once i had a feel for what the team was like and what the competitions were like, i had a better idea of what i wanted to do in the future it takes a lot of paitence to know what you can contribute to the team, and dont worry, you still have a few more years to build and contribute.

think of something that your team has a need for. is it a website? is it promotions at the event? talk to your mentor and brainstorm ideas to help your team grow.

[Donut]

My freshman year I joined the team intending to be on programming. I had the least experience of all the programmers and was initially given a small little job (just code to turn a compressor on and off) so I could learn the language and my job could be easily done if I screwed up. I just looked at the code others made and what they gave us to learn, and asked my Dad (who became a mentor) for help understanding things. Next thing I know, all the programmers except for me and the team lead quit or stop coming due to work, and I had the entire autonomous mode and arm code given to me to do. Now I'm co-programming lead and Vice President of the club.

From personal experience, I say finish what job they gave you, then use that extra time to learn everything you possibly can, you never know how much you might end up helping out!

[Uberbots]

best way to get involved: ask a team who is working on something if they need help.
that way, (if they arent snobs) they will most likely say yes, and bam! you have a prt on the team.

you just gotta make sure (if one dya youhappen to be on the other end) that you dont leave someone out, or even worse discriminate.

just last year, we had one of those kids who would discriminate against the weak (aka, the soft-spoken). The disciminees either left the team, tried to sabotage our robot, and one of them actually got a mad parent involved.
it was ugly, but we got thru it (and made a STRICTLY enforced rule against leaving people out)

u gotta be careful. but ask for help, and ask if help is needed. thats all it takes.

[Dillon Compton]

This is only my second year on a robotics team, and I had a somewhat similar experience on my team my rookie year. I dont attend the school which my team is based out of, but I was asked by the team leader (my dad) to contribute my programming knowledge (which is limited, but more than anyone else's) to the effort. I agreed, and my FIRST career began.

I experienced extreme culture shock my very first meeting.
The school at which my dad teaches is in Philadelphia, and the kids on it come from all over the city...I live out in the suburbs, and am pretty much the stereotypical geek.
It was pretty difficult to prove myself to the rest of the team and to get accepted into the group, but I worked hard, learned what I needed to to contribute to any lacking aspects of the team (in my case I learned much more about programming, memorized all the wiring rules and became head electrician, and was integral in design and fabrication of our arm), and by the end I had gone from 'Dillon' or 'Mr. Compton's Son', to 'D-Rock' or 'Ben'(an affectionate reference to a supposed likeness between myself and Mr. Franklin...). Work hard, prove invaluable to the team, and not only will you have fun, become obsessed, and get accepted; you'll also learn some things!

the forums and the whitepapers on this site are a great resource, and there are some useful link on my teams webpage...[shameless plug]...www.masteryrobotics.com. Click on the "resources" or "links" tabs!

Good luck

-Dillon

[dude__hi]

I know what you mean. Our team is medium sized with about 35 people at the beginning of the school year. Half stop participating after a few months. Then about 6 or 7 people do all the work. It happened every year and once my fellow seniors and I leave the team will be left to 3 juniors.

When I started my sophomore year I felt the same way. I was new and the team had been fairly successful before so I was shunned to the side by the ruling junior class of veterans. I did the small roles but once I started to become more involved I moved up in the ranks. At our regional I was given the responsibility of coach on the field. I was the same at Nationals. The following year I was the driver and I train the rookies. This is my last year and my life has been completely changed by this FIRST experience.

I owe Dean Camen and my mentors more than they'll ever know.

If you don't believe me type my name (Cristian Arcega) in google and find out.

[Eugenia Gabrielov]

Even if you are doing something you don't think is important, you are still a member of the team. Try to completely understand the task you've been assigned, and see if you can improve its design to make it more useful to the robot. Also, even if you are just machining one simple part, you can still be talking to your teammates and getting to know them well.

The better you know people, the more likely they are to give you responsibility. I know that when I started getting to know more people on some of the building sub-teams, I earned more of their respect.

[Nita]

This is my rookie year and I joined having no clue of what this was going to be like. I wasn't even sure of which team I was going to join, so I just went with the flow and ended up joining the manufacturers. On my first day, I learned the names of basic tools and how to use them and all the new members took turn trying them out and practicing. After that, I just did whichever task was assigned to me and when I didn't have anything to do, I watched other people work from their side. When I came home, I got online and looked around to see if there was anything else to learn. You are here on CD, so I would guess that you are equally interested in this program as I am. I showed the team what I can do everytime I had the chance to and now the team has real plans for me next year... I am to help with the design and do graphics for the website while doing all the manufacturing stuff I'm doing this year! Show what kind of things you are good at and you'll get plenty of work to do(just hope that you won't get overloaded).