MSc EE here, self taught in the 8 Bit era. When deciding for EE vs. CS the decision was for something ‚real‘ and not so theoretical. Also I felt the field moved

MSc EE here, self taught in the 8 Bit era. When deciding for EE vs. CS the decision was for something ‚real‘ and not so theoretical. Also I felt the field moved so fast a lot non-math content would outdate quickly. Then only worked with computers doing software all my career. Most of what I learned in universities I forgot. What stuck around and I still leverage today was appreciation for quantities and statistics. Understanding of basic dynamics in linear vs. non-linear systems. A vague feel for frequency and transition responses. An appreciation for materials, their limitations and trade-offs involved in their selection. Not much but very useful and valid forever. When hiring I admit I prefer engineering and physics majors over CS (provided they can code) as former often seem to have more focus on results outside the box while CS are more focuses on the insides. The key to good software with impact are getting the requirements right and that needs negotiations with people outside of the box and making trade-offs.