The bug is the lesson
Why I never hand students working code — and how debugging a stuck motor teaches more than any worksheet.
Read note →11 years teaching robotics and STEM across Grades 5–12 — electronics, coding, mechatronics and autonomous systems, taught the only way engineering sticks: hands on a real build. Ship something that moves, break it, debug it, ship it again.
I was the kid who took apart the remote-control car and could never quite put it back — until, one summer, I could. That gap between 'broken' and 'I fixed it' is the whole reason I teach. It's the most honest feedback loop a student ever gets: the robot either moves or it doesn't, and no amount of memorising changes that.
Eleven years on, I run labs where fifth-graders wire their first LED and twelfth-graders tune PID loops on autonomous rovers. The syllabus underneath is real engineering — electronics, embedded code, mechanics, control — but the surface is always a thing that moves, wins a match, or fails in a way worth debugging.
If your school wants STEM taught as building, not worksheets, I'd love to talk.
From first solder joint to autonomous behaviour — the full build, taught hands-on.
Breadboard to PCB — sensors, actuators, power and safe soldering from Grade 5 up.
Block coding to C/Python — logic, loops and real microcontroller firmware.
Design, 3D-print and assemble drivetrains, grippers and chassis that actually work.
Line-followers to sensor-fusion rovers — feedback, control loops and decision logic.
FLL, WRO and FTC teams — strategy, engineering notebooks and match-day debugging.
Vision, voice and connected-device capstones that put ML into students' hands.
Engineering doesn't stick from a slide; it sticks from a robot that won't turn left. My classroom runs one loop — build, break, debug, repeat — because the debugging is the learning. I don't hand students working code; I hand them a motor, a bug, and the confidence that every problem is just the next thing to solve.
Built the K-12 robotics program and makerspace from an empty room. Runs six competition teams; twenty-two national and regional podiums, and a 400% jump in STEM-elective enrolment.
Grades 6–12 electronics and coding; launched the school's first FLL squad and the after-school maker club now core to the timetable.
Volunteer mentor and judge across regional FTC events; trained rookie teams and other schools' coaches on build and control fundamentals.
Swap these placeholders for real lab photos in the admin panel.
Why I never hand students working code — and how debugging a stuck motor teaches more than any worksheet.
Read note →The safe, scaffolded first-build sequence that gets ten-year-olds shipping real circuits in one term.
Read note →The low-cost kit list and layout that turned an empty room into a K-12 robotics program.
Read note →Sir never told us the answer. Our robot kept turning wrong and he just asked 'why?' until we fixed it ourselves.
AryanGrade 11 · FTC team, 2025My daughter came home talking about PID loops in Grade 8. She wants to be an engineer now. That's all him.
ParentRobotics electiveHe built our entire robotics program and makerspace from nothing. Enrolment and results both exploded.
PrincipalInventure Academy