3 ms·

I'm a software engineer trying to learn hardware. I noticed in the article, the author drew some schematics. These days, I don't use UML to write apps (everyth

I'm a software engineer trying to learn hardware. I noticed in the article, the author drew some schematics. These days, I don't use UML to write apps (everything in my head as I do everything myself anyway, and sometimes I write comments and unit tests), but I remember it being useful during my early days of programming. I'm thinking, since this is my early days of hardware, I should use write schematics (just like I did with UML). Is that a good idea? Where to get started?

frumiousirc 9y ago
The http://fritzing.org/ http://fritzing.org/ application has helped me diagram how to make some simple projects. The mix of physical and logical was useful for me as the circuit boards I used comprised part of the physical design.
jakecopp 9y ago
I find sketching schematics for hardware is a lot more natural than sketching UML, and they're super helpful for making sense of a rat's nest of wires. I can't recommend them enough! I'm a big fan of using paper, it's quite efficient and easy to edit. I only use a design app to present the schematic. Most electronics books will teach you the basics, but this StackExchange answer is a good summary too: https://electronics.stackexchange.com/questions/28251/rules-and-guidelines-for-drawing-good-schematics https://electronics.stackexchange.com/questions/28251/rules-...
manyxcxi 9y ago
I started university as EE, and wound up graduating with Computer Engineering (basically 50/50 EE and CS). 95% of my professional work has been nothing but software, but I've got some (laughably simple) professional hardware experience. I literally can't keep my head straight without sketching some schematics. It's also super helpful when I'm prototyping and tear down a component to build something else (say, to reuse a microprocessor or expensive component like a GSM module) but then I want to go back to that first setup I had previously. Try asking someone who really knows what they're doing for some non-trivial help and show them your rat's nest and no diagram and watch smoke pour from their ears as they try and remain calm and helpful. I think you're on to a good idea though, the UML you practiced provided value (likely not because we all love UML) but it forced you to meditate (for lack of a better word) on design choices and decisions. You began iterating in your head and built some good reflexes. You were practicing your craft in a more robust fashion. I can't imagine spending time with schematics won't be helpful.

frumiousirc 9y ago

The http://fritzing.org/ http://fritzing.org/ application has helped me diagram how to make some simple projects. The mix of physical and logical was useful for me as the circuit boards I used comprised part of the physical design.

jakecopp 9y ago

I find sketching schematics for hardware is a lot more natural than sketching UML, and they're super helpful for making sense of a rat's nest of wires. I can't recommend them enough! I'm a big fan of using paper, it's quite efficient and easy to edit. I only use a design app to present the schematic. Most electronics books will teach you the basics, but this StackExchange answer is a good summary too: https://electronics.stackexchange.com/questions/28251/rules-and-guidelines-for-drawing-good-schematics https://electronics.stackexchange.com/questions/28251/rules-...

manyxcxi 9y ago

I started university as EE, and wound up graduating with Computer Engineering (basically 50/50 EE and CS). 95% of my professional work has been nothing but software, but I've got some (laughably simple) professional hardware experience. I literally can't keep my head straight without sketching some schematics. It's also super helpful when I'm prototyping and tear down a component to build something else (say, to reuse a microprocessor or expensive component like a GSM module) but then I want to go back to that first setup I had previously. Try asking someone who really knows what they're doing for some non-trivial help and show them your rat's nest and no diagram and watch smoke pour from their ears as they try and remain calm and helpful. I think you're on to a good idea though, the UML you practiced provided value (likely not because we all love UML) but it forced you to meditate (for lack of a better word) on design choices and decisions. You began iterating in your head and built some good reflexes. You were practicing your craft in a more robust fashion. I can't imagine spending time with schematics won't be helpful.