Technology

I relate to this strongly. Many of us in this field feel catfished by our jobs. We took the role to get access to exciting emerging tech, or to fulfill some useful purpose and apply strategic thinking. Instead the reality of the day to day is business-led bullshit, drudgery of ticket work for issues affecting one user (and its probably a problem they caused), or having to report progress and "green" status to some talentless PM who doesn't give a shit about you or your career. That and meetings. And fires and escalations and technical bridges.

I worked in IT for years, I'm good at it, I like problem solving, I like fixing things, I like building things.

But as time went by, I found myself in a more managerial role and truth be told, that's not really my jam. And when I wasn't doing that I was the specialist who could support some of our organizations' worst and most troublesome systems. I was also put in charge of training people to use the company's new web app (which was supposed to make people's jobs easier, but really didn't). Let me tell you, I do not like supporting shitty software or hardware, and I really do not like encouraging users to embrace useless web apps that don't work well and serve no real purpose. I hated my job and it was time for a change.

So at that point I decided to completely shift my career and learn to code. I figured, if I hate supporting shitty software, why not just build good software. So I took some free classes through MIT's open course ware, and learned to code. I spent a couple of years coding, picking up skills, learning languages, working with different compilers, taking additional math classes. And by the end of it all, one of my major takeaways was that I do like building things. But... as a professional software developer, I probably wasn't going to be doing a lot of that. At the end of the day I might be able to say, "I squashed some bugs in some code that I didn't write and don't really know the greater purpose of". Or if I'm lucky, "I wrote some functions that took in some inputs and produced some outputs". But that doesn't really feel like building something, that just feels like being a cog in a machine.

Over that same period when I was learning to code I was also picking up a second set of skills. We inherited the home my wife grew up in (which to be sure, is a pretty great deal). But it's a fixer upper, it needed a bunch of attention. And since I was basically home schooling myself I thought I'd earn my keep by doing a lot of that maintenance myself rather than hiring a pro. I collected power tools, I learned to use hand tools, I made a lot of trips to Home Depot. I went through the basement full of rusty tools and restored many of them, replaced handles, sharpened blades, greased gears. I learned how to replace drywall, how to install an electrical outlet, how to repair a dryer. I replaced thermal fuses in kitchen appliances to bring them back to life, I mixed cement and rebuilt a crumbling retaining wall in the backyard.

Over time I got good enough at this that I started helping some of our friends with their homes. I could strengthen a rickety front step, or repaint a room, or replace a toilet. I had skills that people needed and actually, I generally liked doing it.

TLDR: In the time it took me to discover that being a programmer might somehow still not allow me to build things, I also learned that being a handyman would allow me to build things.

So yeah, career changes are scary, and it rarely looks like a good choice, but it is an option. And honestly, I've been a computer guy my whole life, but seriously, working with wood and screws and PVC has been super rewarding. So yeah, I guess I'm saying keep an open mind, and consider trying something different, you never know what might work for you.