View Single Post
  #62   Spotlight this post!  
Unread 21-05-2016, 01:20
gblake's Avatar
gblake gblake is offline
6th Gear Developer; Mentor
AKA: Blake Ross
no team (6th Gear)
Team Role: Mentor
 
Join Date: May 2006
Rookie Year: 2006
Location: Virginia
Posts: 1,934
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
Re: What can FIRST do to increase FRC team sustainability?

Quote:
Originally Posted by Knufire View Post
The argument isn't that removing bag time will level the playing field, or reduce the disparity between rookie and veteran teams.

The argument is that, with the current system, too many rookie teams build robots that simply don't function or accomplish any basic gameplay related task. These teams then get discouraged because they couldn't build a robot that positively contributed to the any of the alliances they were a part of, and decide that the time and effort they put into this program wasn't worth the disappointment at the end. Theoretically, moving to an open build schedule would give these rookie teams more time to reach this bar of performance, where they would have the rewarding experience that Jared's post talks about.
I understand the argument. I simply disagree with it. Struggling teams have plenty of time to build a modest, but useable robot already. That tells me more time isn't what they need. YMMV.

How can time be their biggest problem? A ready-for-inspection kit bot, basic software, and driver controls can easily be built in a weekend, *if* you know what you are doing.

Building the FRC equivalent of a Formula One car, or anything close to it, is not a job for any struggling team. However, the more time healthy teams are given for building, the more their robots become like Formula One cars. As those robots get more sophisticated, the challenge becomes even more difficult for the struggling or new teams who try to keep up.

If you want more teams to survive, make all the robots simpler, cheaper, and less time-consuming.
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
Reply With Quote