When HN users recommended it
1 HN user recommended this in 2025, in one comment.
20072026
Each tall tick is one HN user's first recommendation. A short tick is the same user again. Click a tick to jump to the comment.
1 HN user recommended this in 2025, in one comment.
Each tall tick is one HN user's first recommendation. A short tick is the same user again. Click a tick to jump to the comment.
This is really cool
One thing I'd suggest, for any hardware product, is that when doing your bill of materials to provide links and show estimated costs. Sure, these will change but having a rough idea of the costs is really helpful, especially when perusing on from things like HN. It can be a big difference for someone to decide if they want to try it on their own or not. It is the ballpark figures that matter, not the specifics.
You did all that research, write it down. If for no one but yourself! Providing links is highly helpful because names can be funky and helps people (including your future self) know if this is the same thing or not. It's always noisy, but these things reduce noise. Importantly, they take no time while you're doing the project (you literally bought the parts, so you have the link and the price). It saves yourself a lot of hassle, not just for others. Document because no one remembers anything after a few days or weeks. It takes 10 seconds to write it down and 30 minutes to do the thing all over again, so be lazy and document. I think this is one of the biggest lessons I learned when I started as an engineer. You save yourself so much time. You just got to fight that dumb part in your head that is trying to convince you that it doesn't save time. (Same with documenting code[0])
Here. I did a quick "15 minute" look. May not be accurate
That gives us $200-$280 before counting the power supply and buck converter.[0] When I wrote the code only me and god understood what was going on. But as time marched on, now only god knows.