I'm doing my best to mimic enthusiasm, but it's becoming harder and harder to do so. I was afraid I was turning into a dinosaur, so I tried to be excited about AI. We can do more with computers, we can build faster, we can prototype, etc. But when you have automation you get people with spreadsheets running the business and this is a little bit too close to an assembly line for my liking.
I guess I'll be in the industry until it eventually spits me out, but if the rippling effects of software being devaluated can be so big that I don't know what I'll even do once this chapter of my life is over.
There's truth to this. I find that most of my non-llm work is happening in the "seams" between apps and services - data ownership, security, infra, etc. Things that are happening outside the IDE.
I feel the exact same way and my career path and years in the industry are pretty much the same as well. What's usually blocking me from giving other programming niches a try is that I can't imagine ever building something in them that people actually use. Everything I've studied so far has been grounded in practicality and building a compiler, for example, seemed like something that only a select few can build with good quality.
Anyway, I got the "Writing An Interpreter In Go" book and I think I'll give it a shot either way. I think I'm at a point in my career where I'm finally tired of building the same things again and again. I've also been thinking about doing a design course in Interaction Design Foundation just to get my mind interested in things again and detach myself from the work I've been doing.
I guess I'll be in the industry until it eventually spits me out, but if the rippling effects of software being devaluated can be so big that I don't know what I'll even do once this chapter of my life is over.