Begin away from the equipment
Ask students to write a route as a set of plain-language steps. Another learner can follow the instructions on a grid. Ambiguity becomes visible quickly: a direction without a distance or a turn without a reference point may lead to a different destination.
Connect instructions to intent
When moving to the supported programming environment, ask students to explain each instruction in their own words. Use the kit’s current curriculum and documentation for syntax and device commands. Do not assume a paper plan can be copied directly into working flight code.
Make debugging a learning task
Have students record the expected result, the observed result, and the smallest change they want to test. Changing one part at a time makes it easier to understand the effect. Encourage a reasoned explanation rather than trial and error without notes.
Predict before running
Give a short sequence from the approved lesson materials. Students draw the expected path, annotate each step, and explain which instruction they would inspect first if the result differed.
Program information: Python Flyer overview ↗. Classroom examples on this page are suggested teaching activities.