Back to blog

3,172 Students Proved It: Physical Computing Makes Coding Click

Today · 6 min read

3,172 Students Proved It: Physical Computing Makes Coding Click

99% of teachers in a 2025 Los Angeles County pilot said their students enjoyed computer science more after using a pocket-sized programmable board. Physical computing did what years of screen-only coding lessons had not: it made code feel real.

The board was the BBC micro:bit.

What the evaluation actually found

The source is the independent evaluation of the Micro:bit Educational Foundation's US Pilot 2025, carried out by the Texas Advanced Computing Center (TACC) at the University of Texas at Austin and published in December 2025. With funding from Google.org, the Foundation partnered with the Los Angeles County Office of Education to train teachers in schools serving students historically underrepresented in STEM, give each teacher a kit of 10 micro:bits, and ask them to teach with the boards by October 2025.

The scale was serious: 154 teachers across 84 schools and 28 districts, reaching 3,172 students, mostly in grades 3 to 6. 90% of the schools were Title I schools, serving economically disadvantaged students.

Here is what changed for the teachers:

  • Teachers who felt they had the knowledge and skills to integrate computer science jumped from 42% before training to 82% after.
  • 95% said using the micro:bit resources had increased their confidence in teaching computer science.
  • 97% were satisfied with the training, and 98% said it met their individual learning needs.

And here is what changed for the students, as their teachers reported it:

  • 99% of teachers said students increased their enjoyment of computer science.
  • 96% said the hands-on interaction the micro:bit provided was an important factor in enhancing student learning.
  • 96% agreed students increased their learning skills, like creativity, problem-solving, collaboration and communication.
  • 88% of teachers said at least three quarters of their students were more engaged, 77% said they were more confident, and 72% said they were more interested in pursuing further STEM studies.
  • The students agreed: 85% of girls and 89% of boys who took the assessment said they enjoyed learning with the micro:bit.

One student put it better than any statistic: "My favorite part of using micro:bit was coding what I wanted it to do and seeing my vision come to life."

Why it matters: the screen is the problem

Most coding lessons fail at the same place. A student writes a loop, presses run, and the only feedback is text on a screen that says the same thing either way. Nothing moves. Nothing lights up. Nothing is wrong in a way they can see and touch.

Physical computing fixes that in one move. The code leaves the screen. A button press makes an LED pattern appear. A shake triggers a sound. A sensor reading steers a little robot. When the program is wrong, the robot drives into the wall — and the student can see exactly where their thinking went wrong.

That is why the teacher numbers matter more than the student numbers. The bottleneck in most schools is not student interest. It is teacher confidence. Before this training, fewer than half the teachers felt skilled enough to teach computer science at all. After one summer of hands-on training with a real device in their hands, that number nearly doubled, to 82%. The device did not just teach the students. It gave the teachers something concrete to teach with.

In my classroom

I teach ICT, Computer Science and Robotics in Bangkok, and this matches exactly what I see with my own students. My Year 7s start with the micro:bit too, and the lesson that always lands is the step counter. They code it in blocks in MakeCode, shake the board, and watch the number climb on the LED display. Then I ask them to make it count only real steps, not just any shake — and suddenly they are thinking about thresholds, variables and false positives without me ever saying those words first.

In Robotics, my Year 8s build a line-following robot with an Arduino, and the debugging lesson writes itself. When the robot spins in circles instead of following the line, the students do not stare at an error message. They crouch down, watch the sensor, and work out that it is reading the table instead of the track. The bug is visible. That is the whole lesson: code is not abstract. It has consequences you can watch happen.

Steal this: a 40-minute physical computing lesson

Here is the shape I use, for a micro:bit, an Arduino or any small board you have:

  1. Show, don't tell (5 minutes). Run a finished project in front of them. A step counter, a dice, a traffic light. Let them see the code do something before they see the code.
  2. One new block, one new idea (10 minutes). Teach exactly one thing — an input, a loop, a variable. Never three.
  3. Build in pairs (20 minutes). One student codes, one tests the board. Swap halfway. The tester finds the bugs, because they are watching the board, not the screen.
  4. Show and tell (5 minutes). Two pairs demo what they made. Ask each pair one question: what did you change when it did not work the first time?

Three projects that work in week one:

  • A step counter: shake the board, count the steps, display the total. Teaches variables and inputs.
  • A digital dice: press a button, show a random number. Teaches random numbers and events.
  • A traffic light: red, amber, green, on a loop with pauses. Teaches sequencing and timing.

And one rule that saves every lesson: test on the board early and often. Code that only ever runs in the simulator is a worksheet with extra steps.

The honest caveat

These are mostly teacher-reported outcomes, and the follow-up survey reached 61% of the trained teachers, so the most enthusiastic teachers may be overrepresented. The pilot ran in one US county, in one school year, with funded training and free kits — your school's results will depend on the training and the time you can give it. And the report is an executive summary of the evaluation, not a peer-reviewed paper, so treat the numbers as strong evidence, not final proof.

Even with those limits, the direction is clear. 87% of the teachers planned to keep teaching with the boards. That is the finding I trust most.

Code that stays on a screen is a puzzle. Code that moves something is a skill. Give your students something real to program, and watch what changes.

What is the first thing you would make your students build — a step counter, a robot, or something I have not thought of?


Sources: Texas Advanced Computing Center (TACC) Evaluation Services, Micro:bit Educational Foundation US Pilot 2025 Evaluation Report: Executive Summary (December 2025) — TACC report (PDF). Also cited: Micro:bit Educational Foundation, Los Angeles County Office of Education: bridging the STEM divide — microbit.org.

Title image: original clay artwork created for this blog.

LINE