If you are interested, you can do both. I work for a company that produces machines that tend to get integrated in automation cells for aerospace/automotive parts manufacturers. As the field technician, it's my job to know how our machines play with everything else in that cell so I can fix issues for our customers when things break (and they will break, eventually, for a wide variety of reasons which creates a weird fragility to the whole automation system, but that's a different post).

This requires that I know what's going on mechanically _and_ at what expected behavior of the embedded systems should be (PLCs, device firmware/software packages, network security, etc).

Like you, I was pushed to go to college after high school, only to find out later that college is an industry, not an institution, so the rhetoric about not being able to get a good job without a degree was really just a sales pitch to get my lower-class parents to take out loans they could not afford so me, a veritable child at the time, could make a major decision that would set the tone for the rest of my life. It's a lot of systemically flawed Capitalistic nonsense.

In my field, we _desperately_ need people who understand (at the very least) basic electronics and mechanics, but also the software side of things. The amount of techs from other companies, companies with a much larger and more public reputation than my employers mind you, that do not seem to have a grasp on the basics is astounding and alarming. But even the competent electromechanical techs are weak on how the software or firmware functions, which is often a big key to the "wtf is wrong" puzzle.

I'm not even a coder/programmer, but I know enough to get by and make effort to learn something about programming embedded systems or software for Controls every day, and while I am still an amateur, my god, it gives me quite the edge over a lot of the other guys.

You don't have to be trapped at a desk. Mechanical aptitude can be developed, but it starts by not being afraid to take the screws out and seeing what you can just figure out. The pride you mention comes from that, but you also touched on something else; tangible results. Believe me, I have respect for devs who can create a piece of software from start to finish, but when I manage to bring a slag-crusted horrifyingly-neglected machine back to live after a catastrophic failure that had Automaker X sweating $10000 bullets, it is a real thrill, one that infuses me with great energy for days, sometimes weeks. That's why your friend likes sharing those stories!