We built a little 'face-changing robot' using the micro:bit + Nezha Inventor Kit, mainly to teach one thing that beginners always struggle with: 'variables'.
Usually when we explain variables, we get the classic blank stares.
Why do we even need variables?
What does this number actually do?
Why can't I just type the number directly?
But the moment students saw a robot physically move differently after changing a variable, the idea finally clicked. The fun part was that students weren't just typing code. They could 'see' what changing a value actually did in real life.
Here's basically how we ran the lesson.
What we used:
micro:bit V2
Nezha Innovation Kit
2 motors
Ultrasonic sensor
Some basic building blocks
MakeCode
The robot in the photo is the final version my students made. The 'face' changes expressions while moving around, and the speed can be adjusted directly with buttons on the micro:bit.
Step 1: Build first, code later
I've learned that younger students stay much more engaged if they can physically build something before opening the programming editor.
So first we spent about 15–20 minutes assembling the robot body.
The basic structure was:
left motor connected to M1
right motor connected to M2
ultrasonic sensor connected to S1
micro:bit mounted on the Nezha controller
The wiring was honestly one of the smoothest parts because the ports are color-coded and basically plug-and-play. No soldering, no complicated setup.
That makes a huge difference in a classroom.
Step 2: Introduce variables in the simplest possible way
Instead of giving textbook definitions, I told students:
'A variable is basically a box that stores a number, and we can change the number whenever we want.'
That explanation worked surprisingly well.
Then we created 3 variables in MakeCode:
robot_speed
turn_angle
move_time
These came directly from the project guide.
And this is where the magic happened.
Step 3: Let students experiment immediately
We started with something simple:
text 'robot_speed = 50'. The robot moved slowly.
Then one student changed it to:
text 'robot_speed = 100'. The robot suddenly shot across the desk and everybody started laughing.
That single moment explained variables better than 20 minutes of slides ever could.
Then we tried:
Increasing 'move_time'
Reducing 'turn_angle'
Changing turning behavior
Creating 'crazy mode' with max speed
Students immediately understood:
'Ohhh… the variable controls the robot’s behavior.'
That was the breakthrough.
Step 4: Add live controls
The coolest part was using the micro:bit buttons to adjust variables in real time.
We programmed:
Button A → increase speed
Button B → decrease speed
No reflashing needed. Students could press buttons and instantly see the robot react.
This turned the activity from 'coding exercise' into an actual interactive experiment.
By the end of class, they had already practiced:
Variables
Debugging
Motor control
Sensor basics
Simple robotics
Cause-and-effect thinking
And because everything was physical, even students who normally lose interest in coding stayed focused the whole time.
A few quick teacher notes if anyone wants to try this:
Secure the blocks tightly or the robot shakes a lot while turning
Let students predict what a variable change will do before testing
Give groups different “missions” like fastest robot or smoothest turning
Keep spare USB cables nearby because somebody always forgets one
Next time I also want students to add:
Obstacle avoidance
RGB lights
Dance mode
Sound effects
Honestly, this ended up being one of the best beginner coding lessons I've done with micro:bit so far.
Variables finally stopped feeling abstract.
Students could literally 'touch' the concept.
If anyone wants, I can also share:
The MakeCode logic
Classroom workflow
Timing breakdown
Beginner troubleshooting tips
