My first degree is history and then I did an MSc Comp Sci conversion,mostly on the grounds that it was just one year, and would give me an idea if I liked computing enough to do it as a job, and even if I didn't, having more knowledge in the area wouldn't hold me back in whatever I did end up doing.
I had to keep timesheets for the funding I had, to submit the hours I spent on it each week, and I was regularly doing 70+ hours. It's a hard, intense slog. I am not sure what the percentage was on programming, but part of it was learning the principles of programming, so you could pick up other languages more easily, and also instil good practice like commenting programs (something many of my colleagues have not learned...) Other modules were on things like project management methodologies, networking principles and so on. I came out at the end being pretty certain I didn't want to do programming as a full-time job, because I find it frustrating, though I could do it quite well. I got a job on a 2 year graduate trainee scheme with a blue chip company, so got to move round different roles, which was useful experience. But the MSc (and lack of penis) got me the interviews in the first place.
I still work in tech, in systems admin. I have had external training paid for by my employers over the years in the particular tech skills they want. I would say on a day-to-day basis, I probably use skills from my history degree more - writing and analytical skills, even though it's still a technical role. Programming is probably more solitary, but there are no roles where you can totally avoid working with others. I'm in an area where we do have some colleagues whose social skills are less than ideal (possibly including me, but being the only woman in the department, I at least attract others for the novelry factor...) and they can be a bloody nightmare to work with. It is more effective to work with someone who may not be as technically excellent but tells you what is going on and communicates, than someone who may be technically brilliant,but then produces what they think you should have asked for, not what you asked for (after analysis and discussionwith various stakeholders), and just won't tell you how things are progressing and when you can expect something delivered.
And you can need a strong personality to survive as a woman in the more macho areas of tech, because it can be hard going. It's not the same in all companies or even all departments In tech, but it is still there in places, and women in IT programmes won't fix it, because it's the twatty men with their fragile little egos who won't involve others who need fixing, and I've not yet seen any workplace efforts to sort them out. Fortunately, there are also reasonable, even lovely men who work in the industry. And some have more competent interviewing skills, too...