/electronics/ - Electronics engineering

>>10
It's a great starter book. But i would recommend looking into MIT's corses if you like that way of learning http://ocw.mit.edu/courses/electrical-engineering-and-computer-science/ It has a lot of good stuff and should give you a solid foundation.

>>12

Great! Thanks a bunch!

Sedra/Smith is good imo

Solid chapters, solid problem-set

>>10
If you tell us a little more about your background (math/circuits) we can give better advice I imagine

>>24

Math through multivariable calc, and brief circuit intro in physics 101, but I don't remember anything. Should I get my math squared away first? Also, is learning C at the same time a good idea?

>>25
You're good then. Formal electronics stuff is mostly nodal analysis, KVL/KCL, on MOSFETS and BJTs and Diodes.

You need strong algebra skills but it doesn't get wonky or calculus-y like in AC circuit analysis because you only analyze one frequency range of signal at a time.

In short, you just need strong algebra skills, and to be good at redrawing circuits and seeing when two drawings are nodal-ly equivalent.

I highly reccomend that Sedra smith book, and the chapters on diodes, bjts, mosfets.

Bear in mind though, this is just if you want to be all hardcore about it. You can also very well start playing around with designs you find online. We live in a miracle age where transistors cost literal pennies. Take advantage of it!

>>25
Oh, forgot.

What you're really learning when you learn a programming language is >>how to learn a programming language<< which is infinitely more important than learning a specific language.

Learning to read and write C/C++ well can take a little while, but it is very empowering.

Learning what good software is, and how to design and write it takes considerably longer, but that's true of any language.

But anyhow, C/C++ will get you deep into the guts of your computer if you stick with it.

As to whether you should learn it now, that's up to you, but I advise you not to half-ass it. If you're going to learn, commit to it. Read the philosophy of someone who gives a shit about making good software or don't do it at all. I know a lot of engineers who are very very smart people but who can't program for shit, and who just make hot garbage when they get behind the keyboard. Not because they couldn't fully grok the situation, but because they didn't commit to spending the time to really perfect and learn it. That's how we end up with shit like MATLAB and all the other software written by power engineers and physicists.

Anyhow, I hope that's helpful. Just remember, becoming a good programmer is a lifetime commitment.

>>31

Thanks so much!