3 ms·
Yes, but then there is also a ton of best practices, what works and what doesn't work, basic circuit design principles etc. which to my knowledge isn't really c
by kabouseng 13y ago
Yes, but then there is also a ton of best practices, what works and what doesn't work, basic circuit design principles etc. which to my knowledge isn't really condensed in any one book, but rather in lots of trade articles etc.
(This assumes chip design work (ASIC's etc), but general hardware design (uC work) the same principle applies, and then you don't need the calculus and physics knowledge really).
Sauce: I'm an EE too... :D
- weland 13y ago> Yes, but then there is also a ton of best practices, what works and what doesn't work, basic circuit design principles etc. which to my knowledge isn't really condensed in any one book, but rather in lots of trade articles etc. That's also true about software. Once you get past the usual "comment your code carefully and make sure you're not redundant in it", 99% of the stuff that is useful in practice is stuff you derive from practice.
- vinceguidry 13y agoI'm learning how to test right now. You can read three books about testing, but you won't really get what they're saying until you actually TDD an app. Domain concepts are really malleable (read, hard to nail down) and deadlines are really hard, it would not surprise me if only 1-3% or so of people that work with software seriously actually test their code. I count myself lucky to be able to throw enough work hours in to figure it out. Software is full of thin ice where you can walk out on it, jump around, then, mistakenly thinking it's frozen over, drive your truck on, only to have it fall through. It looks easy. But there's a reason 90% of the Rails apps I've looked at had no tests.