4 ms·
We don’t need to rebuild the ladder, and we don’t need juniors. By the time the seniors leave the job market, the software engineer profession as we know it sim
by Chance-Device 3mo ago
We don’t need to rebuild the ladder, and we don’t need juniors. By the time the seniors leave the job market, the software engineer profession as we know it simply won’t exist. I very much doubt that there will be the higher level architect position either. If Fable 5 is anything to go by, we’re all replaceable within 12 to 24 months. The rest is social inertia.
- pixel_popping 3mo agoFable 5 will be genuinely weak compared to what's coming, I mean, we need to remember this is kinda the beginning still, we will genuinely reach a point where all benchmarks will score 99.9%. Think Opus 10, GPT-10... :) Also Fable 5 isn't "that impressive" as a lot of people have that kind of intelligence since 6 months+ by using combo of models and loops (I scored better on HLE than gpt-5.5 xhigh last January with some good tooling and 6x the cost), but for a lambda Claude Code user, I can see why it looks that good.
- Chance-Device 3mo agoAre you using it or are you just going off benchmarks?
- pixel_popping 3mo agoYeah, saturating 8 Claude Max 20 subscriptions a day, what about you?
- PestoDiRucola 3mo agoWhat makes you think that models will improve with the same pace that they have been improving in the past few years?
- petra 3mo agoA few reasons: -2.5 years is a pretty short time for a new tech development, even if it fails eventually - usually when a new tech is introduced, the biggest gains happen when the environment is changed to fit it. That takes time: libraries, api's, verification tooling, rl environments, skilling users, etc. - possibility of orders of magnitude hardware cost reduction - Optical. Analog. Rram. Many others. Something will work. And internal improvements in the model architecture. And there's scaling in reasoning time.
- pixel_popping 3mo agoExactly, I genuinely believe we are far off from future capabilities, as in models will practically "zeroshot" most use cases without mistakes and it's likely we will directly develop in some sort of language made specifically for AI that is then translated into WASM or the likes which will drastically improve accuracy, there is no point using "human languages" when we will not even be checking codebases (not even filetree) anymore.
- petra 3mo agoIDK. i played with Fable. It's coding abilities are really impressive.
- MattPalmer1086 3mo agoHow will AIs train on new tech without new data to train on? On the bright side, maybe that means the end of new javascript frameworks every 6 months :)
- Chance-Device 3mo agoI think they’ll be writing that new tech, and will be able to read the source code, and reason from first principles. I doubt they will need human generated training data.
- MattPalmer1086 3mo agoI thought training new models on AI generated output leads to model collapse?
- Chance-Device 3mo agoMy point is more that they won’t need new training data to extrapolate to new problems, especially if that new problem is just a new syntax or API. Put the whole shebang into the context. Done. Yes, you need super long context for this, or just pretty good search over it, but I think this is likely to become a solved problem.
- MattPalmer1086 3mo agoAgreed if its just a new API using a current language using common patterns, that is mostly just having a big context. However, the ability to reason generally on novel problems is AGI and we aren't there yet. Eventually in the absence of AGI, we will have to train models on them, and that will require data.
- aytigra 3mo agoI think it case of coding it may not be as bad, because new training data (AI generated code) is always empirically validated by tooling and by consumer. It may not be good but it mostly works, otherwise it is discarded or patched, so it has a bottom bar of "it works".
- whazor 3mo agoActually I believe these agentic models will teach you the value of software engineering faster. You can vibe entire code bases in days and learn more quickly. In my experience with all agents, including Fable, is that they work great when there is automated validation. But as soon as it needs to design something, it just keeps adding so much slop.
- Chance-Device 3mo agoThat’s just the latest position that the goalposts have moved to. They haven’t stopped improving yet, I have no reason to think they’ll stop at the ideation phase. Or any of them, really.
- lurking_swe 3mo agojust the other week I asked Fable 5 to diagnose the cause of some intermittent latency spikes on an API that queries an OpenSearch cluster at work. I encouraged it to look at the datadog metrics, splunk, the whole works. I let it loose to look at whatever it wanted. End result - 2 hours later it produced a convincing theory with lots of references, and burned a bunch of tokens too of course. just for fun we tried its suggestions and deployed them to prod. Guess what? Didn’t fix the issue. Alas, a human was needed after all. either everyone’s working on toy problems, or they’re working on very cookie-cutter code. I’m really not sure. I DO remain impressed with Fable 5 but the idea that we’ll all be unemployed in 2 years is hilarious delusion. we’re already at the point where many organizations are scaling back some of their AI spend.
- Chance-Device 3mo agoBy any chance, is the following true: you had no empirics in the loop. It couldn’t validate any of its theories by experimentation. If the solution requires being able to make actual changes in order to gather more information and it is not allowed to, and this is the only way to solve the problem, by definition it couldn’t do it, nor could you. Or was it something that could be worked out entirely on an a priori basis from the available data? And while we’re talking about hilarious delusions, perhaps you should look at the current capability curve of AI and weigh it against the constant stream of arguments for why it couldn’t have continued at every point and yet has.
- surgical_fire 3mo ago> in the loop Yes, the solution is to just burn more tokens.
- Chance-Device 3mo agoWould you care to say something substantive, or is that just not a thing you do?
- surgical_fire 3mo ago
- boshalfoshal 3mo agowow an actual ai-pilled comment on here for once, I agree with your sentiment. People opining about "rebuilding the ladder" have no idea whats coming for the software industry, and the general populous of white collar work. "Models can code well now but they cant do high level architecture" is just a logical fallacy. Its literally only true in this particular moment in time. But if they can code well, whose to say they wont architect well? And at that point, what do SWEs do? If anything, SWEs are in the critical path of automation for these AI labs anyway, so theres a very strong incentive to automate us out vs other professions, and it'll happen soon. All these random 1-off datapoints of "Fable 5 can't do X very idiosyncratic thing" are completely missing the point. 6 months ago, even attempting that problem with any "tool" would be totally intractable, and now it _just_ writes a slightly subpar solution. You can do some basic extrapolation here, its not that complicated. Your best bet is to just chose a different career, or, if you still want to be in the software industry, be more enterprising.
- mikert89 3mo agoI think it’s 24 to 36 until businesses really trust an autonomous developer. But I agree otherwise
- Chance-Device 3mo agoProbably, might take even longer. That’s the “social inertia” part. I think it’s less trust and more status quo bias.
- QuiEgo 3mo agoI’m always struck by a bit of wonder at comments like this. It seems everyone’s experience is all over the place. Curious, what types of things are you working on where you see these results? I’m at 90%+ code AI generated by stats. I work in embedded systems. It still goes off the rails all of the time and needs a heavy hand to guide it. It does not currently feel like it will ever be truly able to operate independently. It’s a very useful tool, but it’s just not there yet in my day-to-day. Obviously, YMMV.
- Chance-Device 3mo agoWell, I’ll start by saying look at what you’ve just said: you’re in embedded devices, one of the more niche software roles. 90% of your code is written by AI. You’re saying that you need to correct it sometimes. You’ve watched as AI goes from chatbots that literally cannot hold a conversation with a human being to LLMs that can do your job with supervision in less than five years. Maybe your point is just what the difference is to me. It’s competence. On hard problems Fable can just iterate by itself like nothing before. You give it a task, it can plan it, formulate and falsify hypotheses, and do more complex reasoning than anything before it. The main difference is simply that it gets more right and can go deeper on everything. Yes, you do still need to course correct it, but it’s just on the next level. It’s like what everyone experienced when Opus 4.5 came out last year, and the penny finally dropped that AI coding had arrived. If these sorts of jumps happen even one or two more times then it’s all over. It might even be over now and it’s just too expensive to run, but that will change over time. If you can, you should try it and see for yourself.
- orwin 3mo agoI'm in internal tooling for blue and network teams, 70% of my code is generated and I have the same experience as your. The two 'new' hires (1 year into the job, so not so new) however are probably in the same boat as GP, but they just don't see the work we have to put to rewrite their AI-generated issues into something legible and useful, or read their AI-generated PRs filled with duplicated/dead code. Honestly, the biggest improvement AI have brought me is the complete end of my imposter syndrome. People say comparison is the thief of joy,but in my case, previously invisible devs getting more visibility, suddenly pushing new code every week at the same pace as me but clearly without any understanding any of the underlying issues did wonder to my self esteem. I still consider myself among the worst of my group, but my group evolved from 'all devs I know' to 'the competents', which is very nice.