Comment by keybored
1 day ago
I can’t just quit the “career” that I’ve spent years building (for what else?). I’ll just fade somewhat gradually into unemployment, I imagine.
1 day ago
I can’t just quit the “career” that I’ve spent years building (for what else?). I’ll just fade somewhat gradually into unemployment, I imagine.
> can’t just quit the “career” that I’ve spent years building
One, I think the talk about AI replacing developers is tripe. We’re still correcting the post-Covid hiring binge.
Two, even if that level is breached, I’d consider your skillset more broadly than what you can literally do right now. Organizing people and technical systems is hard. And the article highlights how that doesn’t seem to be something AI is focused on improving on right now. (Would take larger context windows. Which would make inference more expensive.)
I firmly believe that your existing skills and experience are more valuable in a world where the AI tools can speed up the bit where you type the code.
It's great that you believe this, but are you hiring?
I don't intend this to read as pure snark, but someone's abstract value isn't much good to them if the job market itself can't / won't recognize it.
This echos my sentiments with trade work and repair skills, everyone claims it is so valuable and rare skills, but the job market doesn't seem to agree with it. There are people with 30 years of experience that could build a house from scratch then go home and rebuild their car engine, but are barely making more than people waiting tables at Olive Garden.
What skills people think are valuable and prized, and what skills corporations are willing to pay for, are often very different.
You’re right. Hiring depends on revenue streams. Code being cheaper means less coders needed for same code. Less-sr-coders-needed means more senior engineers competing for limited architect/leadership roles.
However, the happy path is that as more code is written, more revenue streams will be developed and more sr engineers will be needed and hired to manage those ballooning codebases. That will be a gradual process of growing the pie though.