Quote:
Originally Posted by gblake
"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
|
This is a really long post to tell people to keep posts short...
If this was strictly an "agree" or "disagree" topic then a multiple choice poll would have been sufficient, however there needs to be an opportunity for justification of everyone's point. A TLDR attitude prevents people from having their voices truly heard. Plus, adding a summary to a forum post only makes the post longer.