Quote:
Originally posted by gwross
Thanks Verdey, I knew I was going to have to respond if someone didn't express my position before I had a chance.
Consider: How graciously professional is it to keep secrets just so you can whomp on unsuspecting rookies? (I say not at all!)
|
Gracious professionalism is about
:
1) being good sports
2) helping teams with technical issues
3) not intentionally damaging someone else's creation
4) always trying your hardest
How is everyone devising our own strategies against gracious professionalism? I have no problems with helping the rookie teams wire their motors, program their controllers, attach a shaft to a gear, or so forth; but to say that keeping a strategy secret is against gracious professionalism is way off base (and a bit insulting).
The biggest part of the FIRST experience is the problem solving. "How does our team tackle this problem?"
If everyone is giving away their solutions to the problem, teams will just copy other teams. That's not problem solving, nor is it inspirational. I just made my original post since I think it's better (and more inspirational) for all teams to come up with their own strategies rather than copy off of others.
The whole "if you don't want to read it - don't" doesn't fly. It's like putting a cake in front of a kid and telling him he can't eat it. No matter how hard he tries, eventually he's going to eat it. The solution is to not put the cake there in the first place - in other words, force the kid to make his own cake and learn something in the process.