VEX coding help for coaches who don't code
Lots of VEX coaches are teachers, parents and volunteers who never learned to program. That's normal. Your job isn't to write the code. It's to give students a path, a way to check their work, and a habit of writing down what they changed.
What students need from you
Questions to ask instead of answers to give
- "Where did the robot think it was, and where was it really?"
- "What's the one number you'll change next?"
- "Did you write that change in the notebook?"
- "Can you explain this line to me?" (If they can't, they shouldn't run it.)
What a good code-change log looks like
This is the habit judges look for. Three columns, one row per change.
| What I changed | Why | What happened |
|---|---|---|
| First turn 90ยฐ โ 85ยฐ | Robot hit the wall 3 of 3 runs | Cleared the wall 3 of 3. Still 2" short at goal. |
| Drive kP 10 โ 12 | Stopped short on long drives | Reaches the goal. Small wobble; try kD next. |
| Added tracking wheel | Wheels slipped on fast starts | Ends within 1" every run. |
Keeping it the students' work
VEX expects the robot and code to be the students' own work. Tools, libraries, courses and AI helpers are fine when students understand what they use and give credit. Our notebook and rules guide shows exactly how.
"Isn't this just cheating?"
It's a fair question. autonomy.school teaches kids to write and understand their own code. Every tool here is a starting point they test, tune and explain themselves. Here's how that works in practice:
- Coach teaches before it answers. It explains the idea, then gives a hint, and only shows the fix after the student has tried.
- Copying code takes a quick check. Before generated code copies, the student answers one question about what a line does. The code comes with a credit line for the notebook.
- You can see the learning. Students can print a one-page learning record with their missions, quiz scores and notebook entries in their own words.
The best check is still yours: ask them to explain a line. If they can, it's theirs.

Where autonomy.school fits
autonomy.school gives your team the path and the checks: 30 missions from Blocks to LemLib or JAR-Template odometry, a virtual robot, quizzes, and an AI Coach students can ask at 9 PM when you're not there. The Lab plan covers a whole team.
Questions people ask
Do I need to know how to code to coach VEX V5?
No. Many great coaches don't. Give students a learning path, a way to test their code, and a notebook habit.
How do I help a student who's stuck after block code?
Point them to C++ next, then odometry with LemLib or JAR-Template. A structured course with a simulator lets them practice without the robot.
Is using a course or AI helper allowed in VEX?
Yes, when students do their own work, understand it and give credit in the engineering notebook.
Is autonomy.school cheating?
No. autonomy.school teaches kids to write and understand their own code. Every tool here is a starting point they test, tune and explain themselves. Coach hints before it answers, copied code asks a quick question first, and students can print a learning record.
Try it free. The first autonomy.school missions run in your browser. No sign-up, nothing to install, and there's a virtual robot if yours is at school or the lab.
Start the free missions