View Single Post
  #8   Spotlight this post!  
Unread 29-01-2007, 20:46
JaneYoung JaneYoung is offline
Onward through the fog.
no team
Team Role: Alumni
 
Join Date: Mar 2006
Rookie Year: 2002
Location: Austin, TX USA
Posts: 5,996
JaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond reputeJaneYoung has a reputation beyond repute
Re: Does your team read the ENTIRE FIRST manual?

My post isn't a response to any made - it is something I have been thinking about for awhile. It's a lot of money to lay out for a team to participate in an extraordinary competition called FIRST and to not read the manual or understand the significance of the manual is wasteful. The manual is what keeps the train on the tracks, on schedule, and running smoothly. Without the manual, there is no FIRST competition. So if we don't spend some time studying the rules and understanding them, we are not getting the full benefit of the competition and the money invested. We are doing a disservice to ourselves and to our sponsors by not putting everything we have into the competition.

Reading the manual, reading the updates, using the FIRST Q&A - are ways of investing wisely. If one person is the rules guru for the team, that's great but everyone on the team should be encouraged to familiarize themselves with the process of reading the manual. It is a sound investment.
__________________
Excellence is contagious. ~ Andy Baker, President, AndyMark, Inc. and Woodie Flowers Award 2003

Character cannot be developed in ease and quiet. Only through experience of trial and suffering can the soul be strengthened, ambition inspired, and success achieved.
~ Helen Keller
(1880-1968)

Last edited by JaneYoung : 29-01-2007 at 22:49. Reason: typo