Ask HN: Alternative Careers in the Age of AI
15 comments
I think it’s important to have some kind of domain knowledge that goes with software ability. Not just be a software engineer.
The closest comparison to what’s happening today is writing. In olden times a few in the professional class could write. It was not a common skill. Now everyone can write. There are technically more “jobs that involve writing” and writing skills CAN help you succeed. But very few people have a job just writing.
What people do have are domain specific jobs where a writing skill is more useful. Journalism, Industry analyst, etc.
The future won’t be some small set of software engineers focused only on functional code, it’ll be domain-knowledgeable people that plan out domain solutions, write, code, all in one role.
The closest comparison to what’s happening today is writing. In olden times a few in the professional class could write. It was not a common skill. Now everyone can write. There are technically more “jobs that involve writing” and writing skills CAN help you succeed. But very few people have a job just writing.
What people do have are domain specific jobs where a writing skill is more useful. Journalism, Industry analyst, etc.
The future won’t be some small set of software engineers focused only on functional code, it’ll be domain-knowledgeable people that plan out domain solutions, write, code, all in one role.
Ironically that's where I started my career and now I'm hoping to get back there. I was a data-oriented environmental scientist who happened to code.
But at some point, I slipped into 100% software development roles and I never got over how strange it felt to be siloed, isolated from the domain knowledge on purpose. It was far too easy to "win" the tech struggle of the day but produce nothing of actual value.
Dedicated coders were somewhat necessary to wrangle the tech stack (which itself grew more complex to accommodate more devs, a positive feedback which nearly spun out of control in late 2010s). But now? A single coder with domain knowledge has a shot at wrangling their own tech stack as a part time job, the rest of the time focussed on IRL value. This is the future I want.
Dedicated coders were somewhat necessary to wrangle the tech stack (which itself grew more complex to accommodate more devs, a positive feedback which nearly spun out of control in late 2010s). But now? A single coder with domain knowledge has a shot at wrangling their own tech stack as a part time job, the rest of the time focussed on IRL value. This is the future I want.
That's a great idea, shame I don't know anything (spot the Philosophy graduate!)
I'm a software developer. I didn't exactly lose my job to ai, but I was moved to part-time because now I need only review ai PRs. Even worse, I'm on a visa.
I've always thought about a career in welding. It's a real job that requires a lot of real skills and can be quite lucrative if you're qualified enough. There are a lot of different directions, from welding custom exhausts for cars to industrial underwater welding. It sounds exciting to me.
I've always thought about a career in welding. It's a real job that requires a lot of real skills and can be quite lucrative if you're qualified enough. There are a lot of different directions, from welding custom exhausts for cars to industrial underwater welding. It sounds exciting to me.
I still feel like we're on track for more and more products to become undifferentiated and degrade in quality over time, if we keep this up. I think we'll rebound the other way at some point and the folks who've always been super valuable, the people who can work up and down the product from customer calls to design to engineering, will become even more valuable over time. Aka, these are the people who can differentiate your company from generic AI
Unironically: growing citrus fruits in your own land with your own water source.
Why citrus, specifically? Are they especially profitable?
So I'm asking, what is the escape hatch? Do we all become plumbers? Anyone have a plan?