[Hunter Scott] who has graced these pages a fair few times, has been working on electronics startups for the past ten years or so, and has picked up a fair bit of experience with designing and building hardware. Those of us in this business seem to learn the same lessons, quite often the hard way; we call it experience. Wouldn’t it be nice to get up that learning curve a little quicker, get our hardware out there working sooner with less pain, due to not falling into the same old traps those before us already know about? The problem with the less experienced engineer is not their lack of talent, how quickly they can learn, nor how much work they can get done in a day, but simply that they don’t know what they don’t know. There’s no shame in that, it’s just a fact of life. [Hunter] presents for us, the Guide to Designing Electronics that Work.
The book starts at the beginning. The beginning of the engineering process that is; requirements capturing, specifications, test planning and schedule prediction. This part is hard to do right, and this is where the real experience shows. The next section moves onto component selection and prototyping advice, with some great practical advice to sidestep some annoying production issues. Next there’s the obvious section on schematic and layout with plenty of handy tips to help you to that all important final layout. Do not underestimate how hard this latter part is, there is plenty of difficulty in getting a good performing, minimal sized layout, especially if RF applications are involved.
The last few sections cover costing, fabrication and testing. These are difficult topics to learn, if up ..
Support the originator by clicking the read the rest link below.
