Sorry, there was a bit of tongue-in-cheek to that "analogue stuff" statement...
Before I got into software, one of my hobbies was electronics, so I know plenty about analogue electronics. It's just that digital stuff took over, and even now, I can play with embedded systems where the two sides meet - arduinos, pis etc. Working in telecoms, and PCM-encoded speech, you get very involved in A-to-D and D-to-A - and in my early days, that included the signalling too.
However...
I only know enough to be dangerous. The theory of electronics, up to but not including inductance, coils, and resonance. I understand the basics of motors, generators and transformers ... but not the stuff where RF engineers earn their crust.
Because of that, I don't have the skills to deal with analogue when it gets tricky, and isn't working correctly. To troubleshoot properly.
So I would know what an AGC was for, and could describe why it was beneficial to a system (especially to us on the digital side). I might semi-understand the circuit diagram for one, but I couldn't design one, and couldn't begin to fix it if it went wrong.
I went in the direction of TTL, CMOS, logic, bits and bytes instead.
Edit: But I'm impressed by the feedback in the church. Just to prove that analogue stuff can be weird!