- Mon Nov 26, 2012 9:29 am
#152330
SparkFun, this one's for you!
Hi all, I'm a hobbyist-turned-product-developer. I'm a hobbyist by nature (lots of prototyping & troubleshooting experience, not as much in proper organized documentation), so I'd like to know if anyone has an organized way of collecting information when they iterate a product. I've read SparkFun's Prototyping Tricks and Tips PDF for some tips already, but would like to see a template/system that implements this as I learn better from seeing specific examples.
Ideally, I'd like some sort of Word or Excel template to keep up with design changes implemented, problems found during troubleshooting, schematics, layout, firmware, IOM information, my contact information, and any other important things you may think I'm leaving out. I also could use some advice on some good practices on maintaining such documentation.
Thanks!
Hi all, I'm a hobbyist-turned-product-developer. I'm a hobbyist by nature (lots of prototyping & troubleshooting experience, not as much in proper organized documentation), so I'd like to know if anyone has an organized way of collecting information when they iterate a product. I've read SparkFun's Prototyping Tricks and Tips PDF for some tips already, but would like to see a template/system that implements this as I learn better from seeing specific examples.
Ideally, I'd like some sort of Word or Excel template to keep up with design changes implemented, problems found during troubleshooting, schematics, layout, firmware, IOM information, my contact information, and any other important things you may think I'm leaving out. I also could use some advice on some good practices on maintaining such documentation.
Thanks!