I took up with some TechShop stuff -- before it folded -- and enjoyed my work on laser engravers, and the CNC machines, and the lathes, and whatnot. My educational background and IT experience were certainly a help, and I thought, "Dang, it sure is nice to construct a physical object at the end of the day instead of an arrangement of magnetic fields that will simply be blown away when some high muckety-muck notices whatever fad has changed."
I jumped ship for something adjacent where I use my IT skill constantly. Programming wasn't in the job description, but my ability to program brings a certain level of power. All of my decades of IT experience is very helpful here and I still feel like I am doing something with an actual concrete output and utility.
So, I sympathize with the urge to pull the ripcord on some kind of jetpack and blast far away into the sky, but there are plenty of places that are not what HackerNews thinks of when they think IT that need all of your skills. Perhaps I like being a medium-sized fish in a smaller pond, it could be that, but it does feel fairly nice.
My computing interests lie in automating tasks previously performed by humans, ETL, and analysis. I was doing web stuff back in the 1990s and went through so very many CRUD apps, but this is where my interests lie. What this means in my current job is that I find time-consuming tasks done by my predecessor and say, "Let's make this faster." Or I can look for subtle errors.
Just as an example, because I am routing emergency services to houses and workplaces, I have a network of streets to deal with. Imagine them as a graph, where most of the data is attached to the edge rather than the node. Now, people have drawn these streets in using tools like ArcMap, but there can be problems. How many different kinds of mistakes might exist in connecting roads together? Try to enumerate the cases.
I have found ten thus far. Each case is something that, if a human eyeballs it up close, they could say "oh yes," but it is not readily apparent. And so I have written code for a number of these cases that takes my human domain expertise of what is wrong with something and translates it into something even a rock (silicon) can understand. And the end result of finding these little mistakes is very real: help gets to someone just a few seconds faster.
I interface with organizations that are not other IT organizations: property records, postal records, phone records, and so on. Sometimes this means wrangling proposed plats from developers. It's all real stuff, and it's all done in service of helping people who have immediate needs.
It's very different from being in a room full of people who have little stickers on their Macs making Agile noises about whatever random shifts have occurred in the "client??" (and doesn't that word encompass a multitude of sins)'s latest wishlist.
My guess is that tons of these kinds of jobs are out there because the real world still exists and the people in it are often using computers, but perhaps not as "centrally" to their jobs. However, people like you and I can provide options to them that they did not have before, and sometimes may not have even envisioned. Just as a case in point, this new place was setting up some machines and had a few tedious configuration problems, so I used batch files and a few more things to save them time and add reproducible results. They were shocked but this was stuff for me where I had to dust off things I had forgotten a decade prior.
In my previous job, I found areas of satisfaction as I noticed above, and they were all tied to people (not users), to physical objects (rather than instatiations of some class), and so on. I noticed how much churn there was, how often things would have to be redone not because anything realistic demanded it, but because of style, or some kind of platform migration, or something else End-of-Lifed, and so on. Indeed, constant platform migration made me realize that nomads are not known for their lasting works of architecture.
I was part of that big "brain drain" where someone says, "Hey, you are good with computers, right?" and off I went. I had figured out that the sciences would be long and without a lot of payoff, so I did not look back too hard.
I suppose I got a reputation as someone who gets a far-off look when an interesting problem is described and was asked to apply to my current job because of it, despite it being a different sector and problem set.
I am in my thirties, and a career shift seems more and more inevitable. I seem to have swallowed several blackpills about various industrial complexes and see no bright future of the internet/tech in general, rather the opposite.
What's your age and what is you plan? I am actively looking for some kind of path at the moment for ex-tech people..
If anyone has any input i am all ears!
I have no plan for making money, and I doubt I have enough stored wealth to last more than a decade. Health care in the US being what it is, probably not even that long. These are so far the only reasons I haven't already done it.
Of course just having the right skills isn't the same as achieving the dream. I still have to put in "the work" after I paid the entry fee.