Mythic Comparisons in the Robotics Report

Beyond the Scoreboard: Lessons from the Robotics Floor

1At Saturday’s school robotics competition, Westhaven’s team finished fourth, but the scoreboard told only part of its story. Students had designed a robot to collect foam blocks and carry them through a marked course. Between rounds, their worktable became a harbor in a storm: a place to pause, check equipment, and decide what to try next.

2During practice, the robot crossed ramps smoothly and lifted every test block. Its loose battery connector was its Achilles’ heel. Whenever the robot made a sharp turn, that connection slipped and the machine stopped. The team’s purple banner hung behind the worktable. Before the next round, team member Zuleika secured the connector and tested several tight turns.

3A separate problem appeared when the robot entered a narrow lane. It kept circling instead of moving toward the collection area. “Checking those settings felt like a Sisyphean task,” said teammate Bram. “We reset them, watched another circle, and started over.” The group eventually discovered that an old instruction was being loaded each time the program restarted.

4Zuleika’s testing notebook then became their Ariadne’s thread. Its dated entries showed which changes had worked and which had caused new problems. Following those entries, the students traced the unwanted instruction to an earlier version of their program. They removed it rather than rewriting everything, leaving enough time for one complete practice run.

5With the final round approaching, someone suggested adding a faster lifting motion. “Opening that section now could be Pandora’s box,” Bram warned. Changing the lift could also affect the balance and timing, neither of which the team had time to test again. They kept the slower motion. Their final delivery was steady, though another team completed more trips.

6Afterward, Zuleika called their early confidence “an Icarus moment.” One successful practice had convinced them to increase speed before checking how the parts worked together. “We weren’t wrong to aim high,” she said. “We needed better tests before climbing higher.” While awards were announced, the team recorded its next steps. Fourth place was a comma, not a period, in its work.