Quote:
Originally Posted by Cynette
As a team, in small groups, we read the bulk of the manual aloud to one another (yes, really!) in the workshop we hold immediately after the game is released. In the small groups we discuss what we have read until we know that we have a general understanding of what was read.
|
Definitely a good idea.
[

]You could also have them come on here and ask questions. Just let us know first so the very first response is, "Read the manual!" rather than the answer they want.[/

]
Also, spend the first week of build looking over the rules, designing strategies within the rules, and generally dissecting the rules. Not only will this help with rules knowledge, it may also help give you a competitive strategy. Now, the catch: If someone proposes a strategy/device/design that is against the rules,
they have to find the rule that outlaws it. (Give them the section--we aren't totally mean!) Or, they have to show that it doesn't violate the rules. I bet they'll learn pretty quickly-- if for no other reason than to save themselves from more reading!
__________________
Past teams:
2003-2007: FRC0330 BeachBots
2008: FRC1135 Shmoebotics
2012: FRC4046 Schroedinger's Dragons
"Rockets are tricky..."--Elon Musk
