View Single Post
  #13   Spotlight this post!  
Unread 03-04-2008, 22:01
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: GP? I think not.

Folks,

Whether the original author realized it or not, making a point about students vs mentors in the pits (and extrapolating backwards from that point into the build season) was the core of the original comment. Let's please temporarily forget that the author muddied up the water by extrapolating forward from the pit situation to winning/losing on the field.

With that in mind, would someone please explain to me which of the two possibilities I list below describes the "better" FIRST scenario.
  • Option 1) Mentors draw on experience to do X; and students learn by watching and asking questions.
  • Option 2) Mentors teach students how to do X; students do X with support and guidance from mentors.
If you choose option 2 (and I predict most of us will), and then if you reread the post that started this thread; I'm curious if, in the process, you become more sympathetic to that original author's feelings about pits where mentors appear to be doing most, if not all of the work.

For the life of me I can't think of one good reason why the mentors shouldn't bust their humps teaching (through mentoring) a teams' students as much as the students can/will absorb before/during a build season and tournaments; and then, at the tournament continue to support the students, but let them hold the reins.

Notice that I didn't say doing something else is bad. I did attempt to express that I can't think of any reason why intentionally striving to do something else is better (please remember option 1 and 2 above).

Blake
PS: If someone wants to point out a significantly different third option, I'm listening. Don't let me fall into the trap of viewing this through the lens of a false dichotomy.
__________________
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