View Single Post
  #13   Spotlight this post!  
Unread 08-09-2016, 17:17
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: [FIRST EMAIL] Stop Build Day Survey

"I advocate tightening the current stop-build restrictions because I don't want to see the total FRC program slide too far down the slippery slope of over-emphasizing the competition part of an otherwise well-rounded FRC program." See the next paragraph for an explanation of why I wrote this.

In this thread about a survey about Stop Build Day, I think it would be useful and interesting if each post (even those that are part of a multi-post exchange) began with a short sentence or phrase stating why the poster opposes/supports eliminating, weakening, loosening, tightening, keeping, strengthening (or is undecided about) the current stop build rules.

I think doing that would help sub-topic discussions from wandering too far afield and/or could help avoid people talking past each other.

And - What I think is more important, I think it might very helpful for the person who created the current survey, especially if they choose to create a follow-on survey.

I wrote my one-liner above.

Someone else might write one of these:
"I'm a proponent of weakening the current stop build restrictions because I think spreading the same work over a longer period will reduce mentor burn-out."
"I am a proponent of loosening stop-build restrictions because I think OPR will go up for teams at the bottom of the OPR scale, leading to increased retention of those teams."
Some people might just post a one-liner in order to remind readers about opinions they have already expressed in other discussions.

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

Last edited by gblake : 08-09-2016 at 17:26.
Reply With Quote