logoalt Hacker News

dgellowtoday at 11:30 AM3 repliesview on HN

PEFI/PE4I as a technical reference when you need details about a specific topic, SLOC as an overall introduction to give a good intuition, and M:E for more practical project tutorials, if that’s what we (hobbyists without any formal training) end up with that would be awesome :)

AlphaPhoenix YouTube channel is also a great source of information to clarify theoretical topics. I find it very helpful to just see how he think about electricity in his various projects: https://youtu.be/X_crwFuPht4. And his enthusiasm is contagious!

One personal note: as someone coming from software I find learning electronics pretty hard as it requires a completely different mental model and way to approach systems. Took me years of various failed attempts to finally internalize I have to stop relying on metaphors and shortcuts, and instead understand the actual physics at play to develop an intuition that makes sense. That looks daunting and I thought I would hate that part but in fact after pushing through the first weeks it becomes really satisfying! Accept things take time and that you will be uncomfortable for a while, and move at your own pace. And here LLMs are actually really helpful to clarify topics you’re not sure you understand fully, once you start to learn the terminology (I use instructions that makes it clear they shouldn’t solve things for me and instead evaluate my understanding)


Replies

dekhntoday at 8:46 PM

To me, transistors are the best example of how hard EE can be. I heard "transistor is a switch" or "transistor is an amplifier". So I bought some MOSFETs and tried to use them. No go. Well, I had to learn (through random web pages and some books) that microcontrollers struggle to switch mosfets. Fine. I'll get a gate driver. Then I have to very carefully pick a bunch of resistor values that make my system behave. Eventually, I learn that transistors aren't switches at all, but can be coerced into sort of behaving like switches, but in reality, there is always leakage and a hundred other variables you have to understasnd and control for. You can see one of my threads here: https://www.reddit.com/r/AskElectronics/comments/1omqn4d/con...

show 1 reply
rramadasstoday at 12:52 PM

Also as a person who came to Embedded/Electronics from the Software side, i found the following incredibly useful to bridge the software-hardware gap using MCUs;

1) Introduction to Embedded Systems: Using Microcontrollers and the MSP430 by Manuel Jiménez, Rogelio Palomera, Isidoro Couvertier - https://link.springer.com/book/10.1007/978-1-4614-3143-5

This has more of a hardware interfacing slant than most books on embedded systems which is what a software person needs. Every topic is first introduced in a general way with lots of illustrations and then its application in MSP430 is shown. Hence we can easily transfer our understanding to any other MCU family. A really good textbook for serious students of embedded electronics.

skydhashtoday at 12:02 PM

> as someone coming from software I find learning electronics pretty hard as it requires a completely different mental model and way to approach systems

I went from electronics to software and one thing that has puzzled me is how much people dislike reading docs as in reference manuals. People can get by with sloppy code full of hidden bugs and when those bugs arise they’re like deers frozen by headlights.

Imagine building a circuit without any ideas how it operates. I’ve encountered web devs that don’t understand how http works.