Ask HN: Would you read lessons walking through every step of a hardware startup?
I keep hearing talk about an upcoming "internet of things" and yet I see very few startups building physical products. It's no surprise though! Commercial scale production of hardware is a dark art; a unpredictable and archaic process passed down to new apprentices via direct contact.
So I want to create a site to publish (and link to) content that would teach: soldering, rework, pcb cad, assembly, plastics, textiles, packaging, production in asia, contract manufacturers, QA, import laws, selling B&M, IP concerns, etc. Furthermore I would like more technical articles giving accessible landscape views of microprocessors, wireless solutions, sensors, LCDs, etc.
Everything you would need to build and sell hardware on a commercial scale, really.
Would you read this? What topics would be most interesting?
Would you contribute?
10 comments
[ 3.0 ms ] story [ 26.2 ms ] threadWikis don't do opinion well.
So I think the right solution is a series of lessons owned entirely by each contributor, and then a wiki-like index that organizes and contextualizes the lessons. And of course you can just RSS to all lessons, or to a specific contributor.
I think I can hack that up in drupal.
I'd tune in to an interviewer with some domain expertise and the ability to tease out of people the how-did-this-really-turn-into-a-product answers that no one is really trying to find right now.
Other than myself I haven't met anyone that can take a product from concept through production so you are going to need a huge contributor pool. Also it's not having the information but understanding the process and cultures your dealing with. As an example a couple months ago someone on here contacted me for an idea: the main components were an LCD and the processor. So I told him to find a manufacturer already using those parts and then design his product using their base system. That way he could get scale pricing without having to purchase huge quantities. With my experience I knew what the key components were for his concept, where to look, and who to call. I don't think you can replicate that information in a guide.
Sadly right now I'm too busy to help much. But if you hit a hurdle on a subject feel free to email me with the question.
EDITED: Added stuff
Edit: responding to your edit.
I think you're right that the guide would miss a piece of wisdom like that if it tried to teach in a normal top down way. Some kind of Q&A subsection may need to exist, and it may be a good source of inspiration for new lessons or case-studies that should be published.
Not sure how much I could contribute but I could always share my experiences thus far. I would be an interested consumer for whatever you're doing with respect to hardware startup info though.