The laminated instruction board at the Indi Cars Challenge Station looked reassuringly simple. Green means go. Red means stop. Pink means left. Blue means right. That was it - at least officially.

Cubeotics, a special event at Discovery Cube Orange County, invited kids ages 6 to 12 into a mini world of robotics and friendly competition. At the Indi Cars Challenge station, each child receives a small Indi car robot and a set of colored tiles, then tries to program the car to navigate obstacles - a bridge, trees, boulders - from start to finish.

I was supervising and circulating when I caught a glance from a girl around six or seven years old. She didn‘t raise her hand or call for help. She just looked at me with the kind of “I’m trying, but I don‘t know what to try next” expression that doesn’t need translation. I walked over, ready to point to the four basic colors and move on. Instead, I stopped. The car wasn‘t obeying the simple script I expected. The girl had placed the tiles carefully, but the robot hesitated at the obstacle, pivoted the wrong way, then stalled - as if it was waiting for instructions that weren’t written anywhere. That‘s when I realized the station wasn’t step-by-step at all. It was engineering.

Some tile colors meant more than the poster admitted - slowing down, turning at different angles - and the kids were expected to discover those functions through trial and error. The missing instructions weren‘t a flaw; they were the lesson. I crouched beside her and changed my approach. Instead of telling her what to do, I asked what she wanted the car to do. “Go over the bridge,” she said, pointing at a large tree blocking the most direct route.

We started narrating the robot’s “thought process” out loud: If it goes forward, where does it end up? If it turns, will it face the bridge or the boulder? What happens if it slows down before a tight corner? We treated the tiles like a language and the obstacle course like a sentence that had to make sense. When the car failed, we didn‘t call it wrong. We called it data.

Her car kept overshooting the turn and bumping into the “tree,” even though the path looked right. So we tested one variable at a time: we added a “slow down” tile before the corner, then nudged the turning tile so the sensor could read it cleanly. The next run didn’t fix everything, but it changed the outcome, and that difference told us what to try next. At one point she paused and said, “What if we try this one?”

That moment mattered more than the finish line. The station wasn‘t just teaching kids to code; it was teaching them to iterate: test, observe, revise, repeat. It was teaching them that getting stuck isn’t a failure; it‘s part of figuring it out. When her car finally crossed the finish line, she didn’t cheer like someone who had been rescued. She smiled like someone who had solved something.

I walked away thinking about how many future engineers begin not with perfect instructions, but with one small victory in a system that didn‘t make sense at first - and a decision to keep trying anyway.

<Alice Chae 학생기자 서니힐스 고교 11학년>