I Horowitz and Hill is a LOUSY textbook. And, personally, I find its usefulness as a cookbook overrated.
Going through the Forrest Mims notebooks/cookbooks/etc. for a solution to your problem is generally a way better idea than Horowitz and Hill. The Mims stuff does a really good job of pointing out the pitfalls you're likely to hit as well as the basic pedagogy.
https://m.box.com/shared_item/https%3A%2F%2Fberkeley.box.com...
One might think that it's historically closely tied with the development of the radio and the telephone, see Tesla, Eddison, Bell Labs.
The common wisdom about electromagnetics with regard to EMI and such things seems to be that it's pretty much black magic. Similar for inductor selection in SMPS design.
It's pretty much physics, so a good deal about radiation can be found in medical physics for example, which is simply a different course of study with electronics as a side show, and maybe better as consecutive program for sophomores.
Applied control theory for embedded systems
It is less math intensive and more intuitive and aims at folks with a software background like yourself.
Razavis RFIC is a good one too, but that’s really getting too specialized. Pozar is good for undergrad microwave.
The OP wants to study EE because he has a specific goal. My suggestion was that instead of trying to study everything EE focus only on those subjects that are relevant.
For example: If I was interested in robotics , I would not bother with digital,RF or Analog or eveen communication systems. I woud primarily focus on Control Systems and Embedded Systems.
This is something that I've seen often in self study plans for software development - the "learn everything and then try to use it" rather than "learn what you need to start solving the problem... and start solving it."
In software development this often takes the form of a self-learner learnings Java, JavaScript, Python, C, and C++. Once in an interview it becomes apparent that they don't know enough about any one language to solve a problem in that language.
This is where a university class (and degree) have an advantage - they've got a set of problems for the student to solve (homework and labs) and then take the student through learning specific knowledge to solve those problems.
This also shows what self teaching often lacks - those small problems that can be accomplished as part of learning how to solve the big problems.
In this case, though, I think OP's approach to this shows that they're serious about keeping with it, which is really cool to see.
Hard disagree. Much of the page involves what normally would be electives. You need exposure to some subset, but not all of it.
To give you an idea, my undergrad in EE did not require a course on materials (although it was an elective).
Everything in "Phase 2" was an elective - none was required (although many universities do require the "electronic devices" course).
Needless to say, if everything in Phase 2 was an elective, so was everything in Phase 3.
Also, when I look at pretty much any job requiring EE, and intersect it with the courses I took as an EE undergrad, I find that most courses are not needed. EE (and an EE curriculum) is often quite broad. For any given course, there are plenty of jobs that will need that course, but most EE jobs will not. If the submitter has some specific goal in mind, he won't lose much by skipping courses not related to that goal.
To give you an idea, when I worked as an EE, I had to use basic circuit theory 2 or 3 times, digital logic only once, and the physics of electronic devices a lot. The level of EM I needed was satisfied by high school physics, so I won't even count EM. Everything else I took: Control theory, communications, electronic circuits, power/machines: Never used it.
the book Digital Design and Computer Architecture by Harris and Harris (A RISC V Edition will release soon in 2-3 months, buy that one)
For Electronic circuits choose Microelectronics by Behzad Razavi. Instead of Purcell go for "Engineering Electromagnetics with Ida", it is more intuitive.
And th first book you should start with is "Foundations of Analog and Digital Electronic Circuits"
Then you go for DDCA and Ida in parallel.
The list does give me head scrather, this is too broad to be ever accomplished. My recommendation to redo the list is first find out what piques your interest in EE, Digital hardware, analog hardware or control systems or embedded systems and try to have a self study focus in that concentration.
The way I see it with this plan you are setting yourself up for failure.
Edit:Removed the ditching recommendation as I see it relevant to OP's goals.