There is a particular kind of joy in building something yourself. Not buying it sealed in a box. Building it. Soldering the joints, slotting the boards together, flashing the firmware, and watching a pile of parts wake up and do the thing it was meant to do.
That is the promise of open source hardware projects. A Raspberry Pi that becomes a retro arcade. An Arduino that waters your plants. A 3D printer you built from a kit that now prints parts for the next printer. It is genuinely fun — the kind of fun that makes you forget what time it is.
But there is a catch, and if you have ever tried it you already know what it is.
The parts nightmare
Open source projects are brilliant at telling you what to build. They are often terrible at telling you where to get the stuff to build it.
You find a project you love. You open the README. It says: “You will need a Raspberry Pi 4, a 3.5 inch touchscreen, a stepper motor, a stepper driver, a 12V power supply, some jumper wires, and a heatsink.” Cool. So you go shopping.
Three hours later you are seventeen tabs deep, you have read four forum arguments about whether a DRV8825 works with this board or whether you actually need a TMC2209, and you still are not sure if the screen you found has the right header pinout. You order something. It arrives. The connector does not fit. You wait two more weeks.
This is the part nobody puts in the fun demo video.
Getting the right parts that actually connect
The single biggest reason open source builds stall is not skill. It is compatibility. The parts that look identical are not. A 3.5 inch screen is not the same as another 3.5 inch screen. A stepper motor rated 12V will behave very differently to one rated 5V on the same driver. GPIO headers come in 40-pin and 26-pin. Some hats use I2C, some use SPI, and a few greedy ones want both.
So here is the rule that saves you weeks: before you buy anything, find the project’s bill of materials — the BOM. A good project lists exact part numbers, not vague descriptions. If it only says “a stepper motor,” that is a warning sign. Cross-reference every part against the board you already own. Check the voltage, the pin count, the interface, and the physical mounting holes. Boring? Yes. But it is the difference between a weekend build and a month of waiting on the post.
And when in doubt, buy from sellers who actually show the pinout diagram in the listing. If a listing cannot be bothered to show you which pin is VCC, it is not worth your money.
Where to actually buy the parts
There is no single right answer, but there is a sensible order.
Start with the official store. If a project recommends the Raspberry Pi store, Pimoroni, Adafruit, or SparkFun, start there. You pay a little more, but the parts are genuine, the pinouts are documented, and the support is real. For a first build, that is worth more than the discount.
Then the marketplaces — carefully. Amazon, eBay, and AliExpress have nearly everything, and they have a lot of cheap clones that are nearly right. “Nearly” is the word that ruins builds. Read the questions section. Look for someone who already asked “does this work with a Pi 4?” If nobody asked, assume it does not until proven otherwise.
Kits beat loose parts. If a project sells a complete kit, buy the kit for your first attempt. Yes, it costs more per component. But every part is guaranteed to fit every other part, and that is the thing you are actually paying for. You can always source cheaper parts for build number two.
Why it is worth it — especially for a kid
Here is the part that matters more than any of the above.
An open source build is one of the best things you can do with a child. Not for them. With them.
A kid who builds a tiny robot from a pile of boards learns something a textbook cannot teach: that the world of technology is not magic, it is made. Made by people, from parts, with tools they can hold in their hands. The first time a LED lights up because they wired it, something clicks. The screen is no longer something that just happens to them. It is something they understand, and things you understand you can change.
That is education in its real form. Not memorising what a resistor is. Watching a resistor save a circuit from burning out and understanding, in one small flash of smoke-free relief, why it was there. Reading a pinout diagram teaches patience. Soldering teaches care. Debugging a build that does not work teaches the most useful skill of all — that failure is just a step, not an ending.
And the open source part is the quiet magic of it. Every project they build exists because someone, somewhere, gave their design away for free. When your kid is ready, they can give one back. That is the loop. That is the point.
The short version
Open source projects are fun. The parts are a nightmare if you wing it. Get the BOM, check the pinouts, buy from places that document what they sell, and grab a kit for your first go. Then hand the soldering iron to a kid who is curious about how things work, and watch what happens.
The build is the lesson. The lesson is the fun.