View Single Post
  #12   Spotlight this post!  
Unread 01-06-2016, 18:23
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,933
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 Citrus Dad View Post
I think this is a potentially fruitful strategy. The question is how to got more experienced teams to find it in their best interest to reach out--incentives can be incredibly powerful. I suggest that FIRST announce in September that some form of team work will be needed to score maximum points in the upcoming game. In 2014 it was the assist, this year it was getting on the batter to capture. On the other hand, in 2015 a third robot too often became a liability. FIRST should be delivering a clear message about the benefits of coopertition before the build season starts.
Yes & Thanks for the hopeful thumbs-up.

My suggested criterion/goal would be "Carry out this lesson plan, and you will build a simple robot (plus driver controls) you can (re)use. Additionally, if you fully take the lessons to heart you will learn how to plan and build a custom robot whenever you feel ready to take that plunge".

Because of the uneven nature of help from other teams, I would urge FIRST to produce a set of pre-season-build, how-to instructions/classes that FIRST standardizes. Experienced teams could become familiar with the instructions and supply valuable face-to-face help.

For new teams FIRST might even make completing the simple bot mandatory in teams' rookie years?

For long-established teams going through a rough patch, building the simple bot gets students' and adults' feet back on the ground, (re)teaches technical and/or project mgmt skills that might have been lost, defuses some arguing & churn, is inexpensive with an easy BOM, generally simplifies everyone's season/year, and ensures that the team will have something to show for their work.

However, getting back to your points, help during the pre-season (wherever it might show up) from experienced teams would be a good thing, and coopertition points to make the resulting simple, consistent robots more useful on-the-field would be a good thing too.

Blake
__________________
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