Slashdot Mirror
Books On Electronics For the Lay Programmer?
leoboiko writes "I'm a computer scientist and programmer with no training whatsoever in hardware or electronics. Sure, we designed a simple CPU (at a purely logical level) and learned about binary math and whatnot, and I can build a PC and stuff, but lately I've been wanting to, you know, solder something. Make my own cables, understand multimeters, perhaps assemble a simple robot or two. Play with hobbyist-level electronics. How does one go about educating oneself in this topic? I've been browsing Lessons in Electric Circuits online and it's been helpful, together with Misconceptions About 'Electricity' which went a long way in helping me finally to grok what electric charge and power actually are. I've reached the point where I want an actual dead-tree book, though. Any recommendations?"
It might be that I'm not a particularly good student, but I've never really been able to learn from textbooks unless I already had at least some background knowledge about the subject I was studying. I'm a practicing electronics engineer, and I find that textbooks are a great reference. I also enjoy reading textbooks written on areas where I have some knowledge, but not enough.
That being said, learning something like electronics or signal processing completely from a textbook would be really tough for me. I'm not saying it can't be done, but I think the original poster would be much better off taking a class or two than he would be trying to slug his way through something like the Art of Electronics.
---- I'll take you in a Hunt deathmatch any day.
If you want to just tinker with the digital side and you are willing to learn vhdl or verilog, then get a dev board from Xilinx or Altera. Some of them come with lcd screens, so you can have fun sending output to the screen.
It's corny but there's a lot more of a sense of accomplishment when you get your first LED light blinking on and off than when you write your first Hello World program.
Analog stuff gets pretty deep, pretty quickly. For what you want to do it sounds like you'd be best off learning the bare basics about LRCs and view transistors as digital devices, then cobble stuff together out of TTL components. As a software guy, you'd probably get a blast out of using a PIC or FPGA board since you write firmware, but get to do some hardware stuff too.
DON'T START WITH A TUBE AMP.
They might be simple but the run on a very high voltage and you don't wanna start messing with them until you have experience with other safer circuits.
I you want very, very simple circuits, try guitar pedals or an old AM radio.
You can find lots of schematics online and many of them will have pictures of how to build them.
I think you bring up a good point, I'd just like to counterweight it a bit.
There are very few technical books that are as well written an clear as Art of Electronics. A robotics book might be more "essential" if you are interested in building a robot, but very few of them will extend your understanding and mastery of robots specifically as AoE will extend your understanding of electronics in general.
"Practical" doesn't just means "arts-and-crafts." Theory is "practical" too, when you are faced with a problem that requires an original solution. AoE was not, if I recall correctly, written with the EE student in mind. It was written for people like experimental scientists from whom the ability to understand and design circuits would be a great practical advantage.
If you want to build other people's designs, then by all means restrict yourself to building things that other people have designed or snapping together modules, you can get by without really knowing much about how electronics works. I expect that most robot hobbyists only have a rudimentary understanding of electronics theory, and that's fine for them. But it certainly won't hurt to be able to analyze circuits even design them, and if you avoid AoE because it is not "practical", you're cheating yourself out of one of the best tech books ever written.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
"The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
As an active hardware engineer you don't need that book anymore. Give it to a newbie. I haven't glanced at my copy since the 90s for similar reason. I liked AoE because it is a window on how a ckt designer thinks... "How to think" not "what to think".
It's pretty useless as a display of how to set the bias current for a class A amp for an obsolete transistor. You know, vocational school "training".
But its great for explaining the thought process of, "I want an amp" "I need the following characteristics" "guess I want a class A" "how should I design one?" "here is an example". Yes the last step, the example, is somewhat useless now, but the best part of the book was the other steps anyway. It provides an "EE education" as opposed to "vocational training".
It's like the difference between "history" and "journalism". Or "education" and "training".
Don't go into AoE expecting the wrong thing, or you'll be disappointed.
Go into it with the attitude that it's "EE in 24 hours" and you'll be unhappy. Go into it with the attitude that its a guided puzzle book or a philosophy of EE work, and you'll be happy. It's kind of like Knuth's TAoCP series, in that way.
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger