I'm not sure who exactly this book is for, but it's certainly not for absolute beginners. There is a huge delta between the target audience and the level of understanding and experience someone not knowing a first thing about electronics would typically have.
I can clearly remember sitting there reading about component parasitics, without even having a clear idea how an ideal component behaves, and so on. I was just lacking buckets of context, and it was a painful read with lots of assumptions about the reader's background.
On the other hand, I still think it is a great book, like pretty much everything else from NoStarch. I just disagree on it being suitable as a first book in electronics.
That said, I'm looking forward to the day when I will be on an adequate enough level to read it again -- this time, in its entirety.
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)
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.
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.
For transistors vs MOSFET I really liked https://youtu.be/DKYguNg1vmk as an overview
As an EE, those statements sound so ridiculously reductive. It's like saying, "An oven is a cake-baker."
And it results in confusion for both EE students and non-EE hobbyists who aren't baking cakes - or who don't know about timers and temperature dials.
A lot of electronic books struggle to find balance between super easy projects, very specific cookbook recipes or a laundry list of components.