> In 2026, I’m not sure the software engineering industry will survive another decade. Due to a text predictor ? I'm a daily user of the most recent Claude and while it's amazing at presenting other people's knowledge and reducing cognitive load by filling in the gaps, it's still just a machine that predicts text and that is a limitation which won't be overcome in this generation of such tools which, including resear…
Even if it's "just" a text predictor, it already outperforms the average person in certain domains, particularly software engineering. With all the recent advances in agentic systems like Claude Code and OpenCLAW, these text predictors can iterate and debug faster than the average human. Looking ahead at the next decade, I totally agree with Sean's view here. > I'm a daily user of the most recent Claude and while it'…
I don't know if my job will still exist in ten years
91–100 of 132 posts
Re: I don't know if my job will still exist in ten years
#92I feel exactly this. One thing I will add: while AI is getting really good at _doing_ the software building bits, I haven't yet seen it well integrated into the decision-making and political structure of organizations. Right now, it seems best in the hands of a high-agency individual empowered and able to make changes or 'ship' something, with them acting as the bridge. This of course, is not a technical challenge, b…
Re: I don't know if my job will still exist in ten years
#93> In 2026, I’m not sure the software engineering industry will survive another decade. Due to a text predictor ? I'm a daily user of the most recent Claude and while it's amazing at presenting other people's knowledge and reducing cognitive load by filling in the gaps, it's still just a machine that predicts text and that is a limitation which won't be overcome in this generation of such tools which, including resear…
Re: I don't know if my job will still exist in ten years
#94Earlier quoted context omitted.
Well it’s not just a “text predictor” is it? You can pretend that today we still only have ChatGPT 2 and that there is only pre-training on a large corpus of information, but that simply isn’t true?
> Well it’s not just a “text predictor” is it? It is, by definition, design and architecture a system that produces believable text. Here's a task to give it which pulls the veil right off: Ask it to add tests to a piece of code where code coverage is 100%, but it doesn't actually test functionality 100%. You'll start seeing nonsense sooner or later.
The “just a text predictor” framing was fair a couple years ago but hasn’t kept up. Current models can genuinely identify untested edge cases even when coverage is 100%. You're definitely using the latest and greatest models?
The architecture started as next-token prediction, sure, and yes, human judgment is still required, but that judgment is being captured and integrated too. Every time millions of people use these models, their feedback feeds the next round of improvements.
Also, these models don’t need to replace your best engineers to be disruptive. They just need to outcompete the bottom of the bell curve. For a lot of junior-level work, we’re already getting close.
Re: I don't know if my job will still exist in ten years
#95Earlier quoted context omitted.
i've been advocating for developers to unionize for years, and there'd always be a big group saying "we don't need a union". AI-based job displacement will do wonders for raising class consciousness when it's too late. the best time to unionize is when you don't need a union.
Unions won't do anything for AI based job displacement though, because they don't need you, whether you're in a union or not. I see this going the same way as SAG for example, if AI video or film creation ever gets good enough where a single "director" can make an entire movie themselves with no actors. Unions and indeed any bargaining organization only have leverage when their people are needed, but what happens whe…
Re: I don't know if my job will still exist in ten years
#96It conflates purpose with outcome. I don't accept the premise that software's purpose is to "automate away other jobs". That may be an outcome, but software's purpose is to enable completely new possibilities. Think bicycles of the mind.
The Apollo guidance computer didn't replace astronauts. It made the missions possible in the first place because no human can continually correct the spaceship trajectory every 250ms for 10 days on end.
We're not receiving some cosmic karma. We're more like cotton pickers after the cotton gin. Someone still has to plow and plant.
Re: I don't know if my job will still exist in ten years
#97Earlier quoted context omitted.
i've been advocating for developers to unionize for years, and there'd always be a big group saying "we don't need a union". AI-based job displacement will do wonders for raising class consciousness when it's too late. the best time to unionize is when you don't need a union.
And do what, what buggy whip unions did?
Replacing workers will be used to increase profit margins rather than lower prices because there’s no competition to force prices down thanks to monopolistic consolidation
Re: I don't know if my job will still exist in ten years
#98Earlier quoted context omitted.
I know a lot of people working across portfolio management and tax accounting. Nobody I know of is using LLMs much and frankly their management has started to back-off pushing it more in the workplace. LLMs suit some jobs more than others. Its quite possible SWE's are the only profession massively affected - whether that means a evolution of the role or decline/death is another question.
> I know a lot of people working across portfolio management and tax accounting. Nobody I know of is using LLMs much and frankly their management has started to back-off pushing it more in the workplace. I could say the same thing for software engineers I know as recently as the middle of last year, things can change very quickly. Up until about December 2025 the fact that LLMs would replace us all (SWEs) was the pun…
Unfortunately the workflow of a software engineer has been to do things like asking questions on stack overflow to do their job - to use digital resources scattered across the web - to show examples of code freely across the web.
The workflow of an accountant, portfolio manager etc has nothing to do with accessing and using the web in the same manner. If you did their jobs you’d know this, but you don’t. Right?
Is it really a surprise? Nope. Thankfully writing code isn't enough. So your job is still somewhat safe for now.
Re: I don't know if my job will still exist in ten years
#99Earlier quoted context omitted.
If software engineering goes extinct, a ton of other white-collar jobs will go with it, and we could be in an intractable depression.
I actually think AI has an unfair advantage with software that is making it seem far more capable that it is. Software is entirely text based, and producers have been putting their outputs and problem solving online for free for decades. I think applying AI to other white collar roles that also require problem solving but do not have as much training, will prove much more difficult. Even coding on proprietary dominat…
I honestly figured that’s why everyone is coming out with MS Office plugins for all the models, and MS itself is putting it in the tools.
So if most any company only needs one person to solve limited IT issues, prompt code production and deployment, generate the usual truckloads of excel spreadsheets, and do most of the finance and accounting… it starts to look pretty scary.
Then, what about the people making and maintaining all the facilities for these people we don’t need anymore? The world flipped its lid about commercial real estate when wfh became a thing. That was relatively small and temporary.
Re: I don't know if my job will still exist in ten years
#100> I don’t think there are any genuinely new capabilities that AI agents would need in order to take my job. They’d just have to get better and more reliable at doing the things they can already do. The "just" here is minimizing what has been the crux of the problem for the past ~5 years. This technology has been capable of producing code all this time. The end result has been improving due to massive scaling efforts,…