| 2 | | Much of the Fall (September-December) is spent on training: building the skills we will use during build season. Training should be: |
| 3 | | * Hands-On |
| 4 | | * Fun |
| 5 | | * Self-Paced |
| | 2 | |
| | 3 | Much of the Fall (September-December) is spent on training: building the skills we will use during build season. Training is divided into Overview Training (for all students/mentors) and Advanced Training (more specialized training for students on a sub-team such as control systems or mechanical or operations). |
| | 4 | |
| | 5 | Overview Training should: |
| | 6 | |
| | 7 | * Be on the team wiki (if you don't have access, please let me know asap) - NOT on the Google Drive |
| | 8 | * Provide the big picture (e.g. how the robot works or how funds are raised) |
| | 9 | * Help new students and mentors understand in detail what each subteam does |
| | 10 | * Be fun and light-hearted (dad-jokes '''are''' allowed) |
| | 11 | * Be hands-on as much as possible (include exercises) |
| | 12 | * Be self-paced (many students don't attend every meeting) |
| | 13 | * Use/link to as much existing online material as possible (don't re-invent the wheel) |
| | 14 | |
| | 15 | Overview training should not: |
| | 16 | |
| | 17 | * Cause death by power-point |
| | 18 | * Teach detailed skills (soldering, crimping, Java, milling) |
| | 19 | * Focus excessively on theory (math/physics/etc.) or requires skills/knowledge a freshman might not have |
| | 20 | * Take more than 2-3 meetings per discipline (electrical, software, mech, ops, etc.) |
