The Busy Board Is a Gift That Explains Itself

Uncle Andrew built his nephew an electronic busy board last Christmas. The board itself is a one-off, but the real second gift is the write-up he produced afterward. It documents the decisions he made with the care of a cookbook author writing a recipe someone else could actually follow.

The hardware choices are careful rather than heroic. A PIC18F67K40 microcontroller sits at the center, powered by three AAA batteries. The LEDs share pins through multiplexing, a way to drive many outputs from fewer pins. That choice alone makes the project teachable: you do not need a fancier chip when you can think clearly about time.

The software becomes the quiet star here. Andrew’s code leans on hardware timers and interrupts to run the show efficiently. The Hackaday note calls his explanation "surprisingly deep," but the surprise is telling. A low-stakes toy that could have been wired with a few 555s instead gets a full account of how the code stretches a trio of AAA batteries. The detail is the point.

What makes the board fun, then, is not the LEDs or the switches. A child will mash a button and watch a light blink, and that is fine. The deeper fun is for the maker who reads the log and sees a hard problem solved with a soft touch. The documentation turns a private build into a shared exercise. It is the difference between a gift that says “here’s something I made” and one that says “here’s how you could make it, too.”

The personal register matters. The board was built for his nephew, not a generic user. That constraint forces choices a product would avoid: the layout is fixed, the code is tuned to exactly this hardware. What results is not a commercial toy but a love letter in solder and C. The joy Andrew took in making it is legible in every design note.

That legibility is why the board is worth writing about. The project does not resolve a design argument or advance a technique. It is simply a careful thing, fully explained, offered to a child and to anyone else who reads the post. In a feed crowded with pitches and showcases, a project that shows its work and then stops is its own quiet argument for making things that explain themselves.