Clicking on my /.ID will lead to a tiresome repetition of posts like the following going back years, and experience only keeps telling me I'm right: your great career is mixing IT with another profession.
I just retired as a municipal engineer; I had the Eng degree but also CompSci and was the Waterworks IT guy for several years before they remembered by Eng degree and put me back into construction and maintenance work. I only oversaw the development of our Major Systems like the map-drafting and work-order-tracking that were millions each. But I *programmed* last Friday, and nearly every day of my career, and past (last Friday was near the end of a 6-month post-retirement please-come-back contract). No, it was not major, or even minor, applications. It was smart, VBA-enabled spreadsheets with custom SQL queries embedded that did things Business Objects just could not do. It was little Perl programs on the web server, cgi-bin stuff from the 90's, that provided a hundred people with a custom web-page for their project-of-the-month, and a data-entry form for their updates on it.
I got all these jobs because IT wouldn't touch them. They were too risk-averse to write up a program in hours and deploy it the next day...even if they could have written it without weeks of explanations of our business, processes, and needs. We used to have IT people who worked next to us and needed no briefings, and could be talked into such mini-solutions, but IT hauled them all back downtown in 1995 and after that, you got a new, clueless, programmer every time you called them, and whose boss needed 3 preliminary meetings before authorizing a project with all possible tracking and staging, and checks and, oh, just endless "process". So filling that gap was key to how valuable an engineer I was.
Every time career stuff comes up on /., I write this note again, urging people to not be a "programmer". Be an engineer/programmer or a doctor/programmer or an accountant/programmer. The poster above who noted that a metric shitload of modern programming is embedded in some ways, most of it written by the engineers of the car or appliance or other product of embedding, was one special class of this, but some kind of (other-profession)/programmer is, overall, the better career choice by far.
And for that, the language of choice is whatever language works in that very specific situation. The notion that such stuff can be done by "low level AI" is comical. If my colleagues couldn't explain their mini-app needs to a human being in less than a week, how could they explain it to a pattern on a stone?