We tested a kit on a ten-year-old laptop. Here's what broke.

Selling software that “works on any laptop” is easy if you never test it on one.

So before the kids coding kit goes anywhere near a customer, it’s going through the real test: a clean install on an old, tired, actual laptop — the kind people actually own. Not a developer machine. Not a fresh Windows install. A laptop with history.

The installer pulls everything from our own vault — pinned versions, checksummed files — so what we test is exactly what a customer gets. No special dev versions, no “works on my machine.”

What we expect to find, based on experience:

The installer is never the problem until it is. One blocked download, one antivirus false positive, one Windows version quirk, and the whole “one evening setup” promise is dead. Which is why every file it pulls is checksummed and why the installer checks its own work at the end.

Kids’ software has opinions. Scratch wants a browser that’s up to date. Offline tools want disk space. The kit has to handle the machine as it is, not as the docs assume.

The parent is the real user. The install has to make sense to whoever bought it, even if the seven-year-old is the one who’ll use it.

The friction log from this test becomes the fix list, and the fixed installer becomes the one that ships. It’s slower than just selling it. It’s also the difference between a kit and a ZIP file with ambitions.

We’ll post the results — including the embarrassing ones — when the run is done.