In my 30's I really hit my stride as a developer and system architect. Enough experience, seniority, and autonomy to own and build out large complex systems.
Many, many mid career devs, I fear, will miss this window. They will become reliant on the LLMs more and more. 2 months back, I was asked to backtest an interview question and 2 out of our 3 most senior engineers (both in their 30's) could no longer write a generic method.
I liken this experience to learning cursive as a kid. It wasn't about writing cursive; it was about developing dexterity and hand-eye coordination. Getting the reps in, so to speak. Even if the future is all AI, that window of expanding one's knowledge and understanding of system design and architecture through hands-on experience (and failure!) facilitates the formation of "taste" through reps: why A over B or C. When B over A or C?
Many, many devs will end up "going nowhere". They will be able to prompt and push code with the façade of productivity, but I think building stable, scalable, complex systems requires knowing which angles to probe and which questions to ask; things learned via reps of trying, failing, learning, failing some more, thinking hard, drawing it out, and finally hitting the breakthrough.
I recently published a series of blog posts that focuses on the underlying architecture decisions that I think can help teams set a solid foundation for building with AI [0]. I think the guidance and patterns in it are unlikely to be emergent from an LLM without very explicit prompting. The goal is to share the thought process and intent for each technical decision. I think this type of thinking may become more rare as folks surrender their reps to LLM defaults.
> No one is going to write new UI libraries if SOTA models know React best, no one is going to bother with new languages if SOTA models know Python, Go, JavaScript, and so on the best.
And here I sit with my own native cross-platform GUI library, made with my own Lisp-To-Rust programming language... Tell me more about what we all are not doing :)
> And here I sit with my own native cross-platform GUI library, made with my own Lisp-To-Rust programming language...
Currently working on something like this. Do you have a writeup somewhere? Specifically how you solved cross platform rendering equivalence? Do you use an intermediate representation or just pure vis-a-vis splatting via native APIs?
I don't (yet), but do subscribe to the RSS feed on my website, I'll publish a writeup there once I've fleshed out exactly how it has to work for all the applications currently using it.
> Specifically how you solved cross platform rendering equivalence? Do you use an intermediate representation or just pure vis-a-vis splatting via native APIs?
In short, my current approach is something like a small renderer-neutral display-list IR, then each frame produces ordered DrawOps in logical coordinates, which then a shared renderer applies transforms, clipping, opacity, paths and whatever, which finally dispatches to platform canvas implementations backed by native APIs.
It's about ~50K LOC in total right now, to support Linux (Wayland + X11), macOS, Windows, iOS, Android, Sailfish OS and headless/offscreen rendering variants for each of those. This is like the 3rd iteration on this library, and for the first time I managed to get all the features in place without reaching +100K LOC, so feels like a pretty good approach so far.
The equivalence is semantic and conformance-tested essentially, not guaranteed pixel-perfect. For me, consistent design across the platforms is more important.
But who cares if they gain traction? I don't need it to gain traction for me to be able to make use of it correctly and efficiently. In fact, I probably need the opposite, for it to not gain traction, so I can focus on using it and improving it for myself only.
gist was certainly not implying that it was not possible to do it or that some people won't continue doing it but the point was rather that the pool of such people or such projects will significantly decrease because software has now (mostly) reached the abundance state where all of these technical details start to matter less and less for general consumption.
We might not even need libraries after all, since APIs, libraries and abstractions in general exist for humans to grasp complexities. Abstractions have their merits, but they have downsides too, and AI might be a way to solve them. The interesting part for me is where that ends, because it's systems all the way down, and even on a higher level abstractions exist to allow humans to make sense of the world. Services, products, companies, political parties, what if in the future we don't need any of it anymore because the abstraction is obsolete?
Libraries do a LOT more than that. Abstractions also make LLMs more efficient, and lets some problems be handed off to much cheaper algorithms. They also mean that the way data is handled can be standardized which means you don't have to design an entire protocol from scratch every time you want to send data somewhere.
Every advantage libraries have given us still exists in the world of AI.
The efficiency argument I accept, it's surely one main driver why systems tend to form and centralize and one important factor in the balance. Still, one can observe the weird things humans and AIs do when trying to dance around the gaps in leaky abstractions. So there's a tradeoff between (the effort spent on) that, and dropping the abstraction completely, as soon as the abstraction stops being a necessary constraint (due to the limited capacity of a human brain).
What about readability? Are people going to give up on reading and understanding the code? Maybe the abstractions aren't only necessary for writing the code?
I think the answer to this is yes, it'll be just like "reading and understanding your assembly". We just don't check what instructions your code compiles down to anymore, and I think the same will be for code.
> you might find the quality subpar, but in terms of cost ratio, it is commercially good enough. Business will accept 99.99 at fraction of cost of 99.999.
It is based on Anthropic Uptimes. If anthropic wanted 99.999 they will have to acquire 10 times more GPUs/infra to match the traditional free resources of 99.999 services.
Personally, based on over a decade of professional software engineering experience at all sort of organisations, from small startups, Government, big tech, financial services of all scale.
In terms of literature, you can look into "enshiftication" as a starting point into research around cost savings and value extraction in business.
Also, about 7 years ago, I had some ideas about how AI will pan out, and here is the releveant excerpt from it:
> [S]oftware development industry, the very workhorse of automation and tools of efficiency is eating itself away. The outward image may look very different with the software development becoming an integral part of more and more industries, yet, the number of developers required for a project of given complexity is reducing at unimaginable rate.
It serves to aggrandize whatever softer basis might actually exist for the conclusion. Whether that's deliberate or the result of thoughtless use of useless platitudes, it's done with a disregard for honesty.
Tricky to make predictions based on costs or quality when the costlier parts, training and inference, are totally disconnected from reality thanks to VC money and when total cost of ownership over time is radically different.
I don't think "new libraries and languages, ... won't gain traction". I think that a higher standard is expected for a new library or language to gain traction.
I foresee the entire "technology adoption lifecycle" of innovators, early adopters, early majority, late majority, and laggards will be longer due to the relatively higher expense of adopting a new technology. I don't think it is a bad thing, but it might delay the adoption of promising tech in industries.
Meaningful library/language improvements will have their benefits, regardless if the user is a human or an LLM. Therefore, their adoption will see benefits as well, eventually.
True intelligence should not have problems adapting to new programming languages. Especially with good TTD and other harnesses, current SOTA models are likely very capable of writing code in esoteric languages
> Software Engineering as science will be largely dedicated to AI development
Which will require fewer people.
Simple software engineers who work on CRUDs and are not PhD-s and stuff will go away. Most of software is like this. The few percent who work on kernels, AI models, etc. will still have work. The rest won't, or rather much less people will be needed to simply use AI to do that work.
Yep. The CRUD-ish part of CS is gonna end up like the typewriter pools from the '60s. Claude code is already way better than most subcontractors I've worked with, and without any weird interpersonal or contractual issues usually associated with whatever sketchy agreements their employers have with my employers.
I can see the ground crumbling in a linear fashion, moving straight towards my direction. In a sense, I've already made peace with that. I know what my skill ceiling is.
I'm decent enough to work on an ecommerce, customer portal or whatever. I'm also fully aware I'm never going to be able to write a kernel module, improve some low level loop in a database runtime in C, or do some sophisticated data analytics or fluid simulation modeling.
My time as developer is nigh. I won't really miss it one bit, to be honest.
Honestly I've been thinking about moving into hospitality, tourism or any other field where AI as zero chance of being able to make a serious dent. At least until robots will be able to give an interactive guided of a museum or a national park.
But right now AI assisted development isn't really making you more productive by an order of magnitude. It's easily a game of whack-a-mole right now. I estimate that an excellent programmer equipped with Claude Code only sees a 30-40% improvement in speed right now
What you speak of may happen, but I doubt it will happen in the next 10 years.
Sometimes I feel the same but then I sit in a refinement meeting and have to handhold the stakeholders through the process of finding out what they actually want, what they don't want, which trade offs they find acceptable and which they don't. And while AI is infinitely patient, my feeling is that being good at this is a super individual people skill and I know that more often than not the people I am talking to are kind of happy they are talking to a person instead of a machine. However when it comes to actually implementing the stuff, AI reliance is now necessary with the timelines given.
Software engineering has been getting more efficient for decades and over that time there’s been a massive increase in the number of software engineers.
The Mythical Man-Month describes teams of ten engineers operating before the Internet. Today (pre-LLMs) that’s probably 1-2 people.
It is a fair criticism from a purely objective and "means to an end" point of view of Software Engineering, but for a lot of people it is also a passion.
> No one is going to write new UI libraries if SOTA models know React best, no one is going to bother with new languages if SOTA models know Python, Go, JavaScript, and so on the best.
Eh, you just don’t get how people work. You might be right overall, or maybe not.
People will write new UI frameworks and languages if the problem seems interesting to them. There are loads of people who just like working on interesting problems, and that’s very unique to each person. They may use AI, they may not, but as long as people get deeply sucked into interesting problems, we’ll still see new ideas and projects.
Or, look at react. It was invented because Facebook was running into issues writing big web UIs. Many companies still have issues writing these, and if they have issues, it’ll be a way they can differentiate and compete. What happens when someone turns an AI on the optimization problem and invents a bespoke in-house tool that’s actually fantastic? That’s another way you could get new tools.
1. If majority of developers use LLMs for coding, and then if someone developed a better React, then no one can really use it because the models does not know how to write idiomatic code in it. It might be easier to make the LLM implement workaround for the issue with the current React, than making it use an unfamiliar library or paradigm.
3. Without some critical adoption rate, the new library won't have enough training material, and this becomes a chicken and egg problem. This can only be broken by AI companies by somehow training the models on the new React by code explicitly written, but again, without critical adoption, there is no incentive for them to do it.
Imagine we are living in the time of jquery and all the LLMs are proficient in it. I don't think in such a world, no one would want Angular/React, because LLMs will happily handle all the complexity that using jquery results in.
New libraries can be used with LLMs directly without training using skills. If you work in a company with bespoke frameworks, you can see this happening. This + RL post training would be the new cycle of adoption.
"People will write new UI frameworks and languages if the problem seems interesting to them."
I would think even with AI assistance industrial quality solutions (which is what we are talking here I think ) still require corporate size sponsor to thrive.
Yes, anyone will create whatever suits their fancy. But there is huge gap between hobby project and industrial adoption.
Exactly. And you can already see the direction things are going with most Web and React Native UI libraries converging on tailwind, since it is extremely genai friendly.
So basically the code generator chatbot - who is trained on source code available on the internet, so by all means mediocre - is now good enough for all software development to depend on it? It's an awful regression.
> This might sound obvious, but it is worth putting it down, Software Development going forward will be largely done by AIs, you might find the quality subpar, but in terms of cost ratio, it is commercially good enough. Business will accept 99.99 at fraction of cost of 99.999. It is all about general consumer expectations, which will shift.
This is correct but a misunderstanding of "who does software development". It's no different to claiming "compilers will do software development from now on". LLMs are simply a metaprogramming tool.
> But most of all, not just that we are not going back, we are also not going anywhere. Software Engineering as science will be largely dedicated to AI development and outside of this discipline, it will slow down to a grinding halt.
Wrong. In fact due to the advances in LLMs we finally have the tools to optimize the underlying foundations. Historically, writing something from scratch or messing around with low-level implementations was out of the question for anyone but the most massive tech firms. Now a small(ish) team can experiment with building a custom VCS and CI/CD pipeline from scratch, without relying on Git. In fact, I'd argue that most current software is _no where close to the optimum yet_.
> No one is going to write new UI libraries if SOTA models know React best, no one is going to bother with new languages if SOTA models know Python, Go, JavaScript, and so on the best.
Dead wrong, on all fronts. And it shows that the author doesn't even understand what LLMs do. I wrote a custom DSL Lisp like language (entirely custom forms and relatively custom syntax) that the LLM understands perfectly through BNF forms + examples. And the domains it's used in (robotics) gives absurd results. Literally outperforming the competition by miles. Pre-LLM this wouldn't be doable without sinking years of dev time.
> Yes, it will be easier for people to build new libraries and languages, but they won't gain traction. This might be different for large corporations who can afford to train and finetune models on their new fangled technology, but that will be the exception, and likely struggle with building a community and talent pool outside of this developing organisation as other people may not fancy using or even have access to their internal models.
Irrelevant. In fact, custom building specific purpose code is far more attractive than it ever was. Why do I care how widely used a library is if it serves my use case perfectly? Historically, again, you had to wrestle with library conventions and styles just to get something to work. Now you can have a microoptimized library built _exactly_ for your use case. " This might be different for large corporations who can afford to train and finetune models on their new fangled technology" -- wrong, you don't need to retrain models at all to understand custom libraries. Again, I have a near entirely in-house written stack (proprietary, never seen the light of day) and LLMs understand it _perfectly_. In fact they can even write perfectly idiomatic code in them, despite it being obscure as all hell, example
ox::app app;
app.add_resource<users_view>(ox::sv{ "/users" });
app.add_resource<user_view>(ox::sv{ "/users/:id" });
auto admin = app.group(ox::sv{ "/admin" });
admin.use(ox::basic_auth(ox::sv{ "admin" }, [](ox::sv u, ox::sv p) { return u == ox::sv{ "root" } && ox::ct_equal(p, ox::sv{ "toor" }); }));
admin.get(ox::sv{ "/stats" }, [](context &c) {
micron::string b{};
b.append("hello ", 6);
const ox::local_value *who = c.get_local(ox::sv{ "user" });
if ( who && who->is<micron::string>() ) {
const micron::string &s = who->cast<micron::string>();
b.append(s.c_str(), s.size());
}
b.append(", here are the admin stats\n", 27);
c.text(200, ox::sv{ b.c_str(), b.size() });
});
> In fact, custom building specific purpose code is far more attractive than it ever was. Why do I care how widely used a library is if it serves my use case perfectly? Historically, again, you had to wrestle with library conventions and styles just to get something to work. Now you can have a microoptimized library built _exactly_ for your use case.
Sounds like OP and you mostly agree on this, although you both make the same point in different ways. If everyone is building specific internal libraries, no library is going to take public traction like it used to happen.
But yeah I agree with you that now specific internal ad-hoc tooling is much easier to achieve also for small shops than before.
N years down the road, 3 year old children can just tell AI to generate a custom game or cartoon for them on the spot.
What's left for humans to do?
Live on UBI, explore this wonderful world, colonize other planets..
And along the way, while anyone can make anything they can think of, it'll come down to who has the better idea, we might enter an Economy of Ideas, and maybe the Idea Guys™ will finally have their day :)
Many, many mid career devs, I fear, will miss this window. They will become reliant on the LLMs more and more. 2 months back, I was asked to backtest an interview question and 2 out of our 3 most senior engineers (both in their 30's) could no longer write a generic method.
I liken this experience to learning cursive as a kid. It wasn't about writing cursive; it was about developing dexterity and hand-eye coordination. Getting the reps in, so to speak. Even if the future is all AI, that window of expanding one's knowledge and understanding of system design and architecture through hands-on experience (and failure!) facilitates the formation of "taste" through reps: why A over B or C. When B over A or C?
Many, many devs will end up "going nowhere". They will be able to prompt and push code with the façade of productivity, but I think building stable, scalable, complex systems requires knowing which angles to probe and which questions to ask; things learned via reps of trying, failing, learning, failing some more, thinking hard, drawing it out, and finally hitting the breakthrough.
I recently published a series of blog posts that focuses on the underlying architecture decisions that I think can help teams set a solid foundation for building with AI [0]. I think the guidance and patterns in it are unlikely to be emergent from an LLM without very explicit prompting. The goal is to share the thought process and intent for each technical decision. I think this type of thinking may become more rare as folks surrender their reps to LLM defaults.
[0] https://chrlschn.dev/blog/2026/08/the-unexpected-ai-stack-cs...
And here I sit with my own native cross-platform GUI library, made with my own Lisp-To-Rust programming language... Tell me more about what we all are not doing :)
Currently working on something like this. Do you have a writeup somewhere? Specifically how you solved cross platform rendering equivalence? Do you use an intermediate representation or just pure vis-a-vis splatting via native APIs?
I don't (yet), but do subscribe to the RSS feed on my website, I'll publish a writeup there once I've fleshed out exactly how it has to work for all the applications currently using it.
> Specifically how you solved cross platform rendering equivalence? Do you use an intermediate representation or just pure vis-a-vis splatting via native APIs?
In short, my current approach is something like a small renderer-neutral display-list IR, then each frame produces ordered DrawOps in logical coordinates, which then a shared renderer applies transforms, clipping, opacity, paths and whatever, which finally dispatches to platform canvas implementations backed by native APIs.
It's about ~50K LOC in total right now, to support Linux (Wayland + X11), macOS, Windows, iOS, Android, Sailfish OS and headless/offscreen rendering variants for each of those. This is like the 3rd iteration on this library, and for the first time I managed to get all the features in place without reaching +100K LOC, so feels like a pretty good approach so far.
The equivalence is semantic and conformance-tested essentially, not guaranteed pixel-perfect. For me, consistent design across the platforms is more important.
Every advantage libraries have given us still exists in the world of AI.
Perhaps we will go from:
framework X -> avoid writing boiler plate
to
AI -> avoid writing boiler plate
And AI may generate the more explicit boiler plate more reliably directly, than the higher level framrwork with leaky abstractions.
> just do “natural language” to a programming language
What is this based on?
It might turn out AI does all programming in future. But it also might turn out that it's incapable of long term maintenance. We don't know yet.
In terms of literature, you can look into "enshiftication" as a starting point into research around cost savings and value extraction in business.
Also, about 7 years ago, I had some ideas about how AI will pan out, and here is the releveant excerpt from it:
> [S]oftware development industry, the very workhorse of automation and tools of efficiency is eating itself away. The outward image may look very different with the software development becoming an integral part of more and more industries, yet, the number of developers required for a project of given complexity is reducing at unimaginable rate.
https://gist.github.com/omeid/9a180f9acccc8409d6c5f3e7fa1a77...
I foresee the entire "technology adoption lifecycle" of innovators, early adopters, early majority, late majority, and laggards will be longer due to the relatively higher expense of adopting a new technology. I don't think it is a bad thing, but it might delay the adoption of promising tech in industries.
Meaningful library/language improvements will have their benefits, regardless if the user is a human or an LLM. Therefore, their adoption will see benefits as well, eventually.
Which will require fewer people.
Simple software engineers who work on CRUDs and are not PhD-s and stuff will go away. Most of software is like this. The few percent who work on kernels, AI models, etc. will still have work. The rest won't, or rather much less people will be needed to simply use AI to do that work.
I can see the ground crumbling in a linear fashion, moving straight towards my direction. In a sense, I've already made peace with that. I know what my skill ceiling is.
I'm decent enough to work on an ecommerce, customer portal or whatever. I'm also fully aware I'm never going to be able to write a kernel module, improve some low level loop in a database runtime in C, or do some sophisticated data analytics or fluid simulation modeling.
My time as developer is nigh. I won't really miss it one bit, to be honest.
Honestly I've been thinking about moving into hospitality, tourism or any other field where AI as zero chance of being able to make a serious dent. At least until robots will be able to give an interactive guided of a museum or a national park.
What you speak of may happen, but I doubt it will happen in the next 10 years.
The Mythical Man-Month describes teams of ten engineers operating before the Internet. Today (pre-LLMs) that’s probably 1-2 people.
Eh, you just don’t get how people work. You might be right overall, or maybe not.
People will write new UI frameworks and languages if the problem seems interesting to them. There are loads of people who just like working on interesting problems, and that’s very unique to each person. They may use AI, they may not, but as long as people get deeply sucked into interesting problems, we’ll still see new ideas and projects.
Or, look at react. It was invented because Facebook was running into issues writing big web UIs. Many companies still have issues writing these, and if they have issues, it’ll be a way they can differentiate and compete. What happens when someone turns an AI on the optimization problem and invents a bespoke in-house tool that’s actually fantastic? That’s another way you could get new tools.
1. If majority of developers use LLMs for coding, and then if someone developed a better React, then no one can really use it because the models does not know how to write idiomatic code in it. It might be easier to make the LLM implement workaround for the issue with the current React, than making it use an unfamiliar library or paradigm.
3. Without some critical adoption rate, the new library won't have enough training material, and this becomes a chicken and egg problem. This can only be broken by AI companies by somehow training the models on the new React by code explicitly written, but again, without critical adoption, there is no incentive for them to do it.
Imagine we are living in the time of jquery and all the LLMs are proficient in it. I don't think in such a world, no one would want Angular/React, because LLMs will happily handle all the complexity that using jquery results in.
We would have stuck with JQuery forever..
I would think even with AI assistance industrial quality solutions (which is what we are talking here I think ) still require corporate size sponsor to thrive.
Yes, anyone will create whatever suits their fancy. But there is huge gap between hobby project and industrial adoption.
There are many, for every web design framework (for React/etc or PHP).
So yes, people write new libraries. The question is how they’re going to write them in the next 5 years.
> This might sound obvious, but it is worth putting it down, Software Development going forward will be largely done by AIs, you might find the quality subpar, but in terms of cost ratio, it is commercially good enough. Business will accept 99.99 at fraction of cost of 99.999. It is all about general consumer expectations, which will shift.
This is correct but a misunderstanding of "who does software development". It's no different to claiming "compilers will do software development from now on". LLMs are simply a metaprogramming tool.
> But most of all, not just that we are not going back, we are also not going anywhere. Software Engineering as science will be largely dedicated to AI development and outside of this discipline, it will slow down to a grinding halt.
Wrong. In fact due to the advances in LLMs we finally have the tools to optimize the underlying foundations. Historically, writing something from scratch or messing around with low-level implementations was out of the question for anyone but the most massive tech firms. Now a small(ish) team can experiment with building a custom VCS and CI/CD pipeline from scratch, without relying on Git. In fact, I'd argue that most current software is _no where close to the optimum yet_.
> No one is going to write new UI libraries if SOTA models know React best, no one is going to bother with new languages if SOTA models know Python, Go, JavaScript, and so on the best.
Dead wrong, on all fronts. And it shows that the author doesn't even understand what LLMs do. I wrote a custom DSL Lisp like language (entirely custom forms and relatively custom syntax) that the LLM understands perfectly through BNF forms + examples. And the domains it's used in (robotics) gives absurd results. Literally outperforming the competition by miles. Pre-LLM this wouldn't be doable without sinking years of dev time.
> Yes, it will be easier for people to build new libraries and languages, but they won't gain traction. This might be different for large corporations who can afford to train and finetune models on their new fangled technology, but that will be the exception, and likely struggle with building a community and talent pool outside of this developing organisation as other people may not fancy using or even have access to their internal models.
Irrelevant. In fact, custom building specific purpose code is far more attractive than it ever was. Why do I care how widely used a library is if it serves my use case perfectly? Historically, again, you had to wrestle with library conventions and styles just to get something to work. Now you can have a microoptimized library built _exactly_ for your use case. " This might be different for large corporations who can afford to train and finetune models on their new fangled technology" -- wrong, you don't need to retrain models at all to understand custom libraries. Again, I have a near entirely in-house written stack (proprietary, never seen the light of day) and LLMs understand it _perfectly_. In fact they can even write perfectly idiomatic code in them, despite it being obscure as all hell, example
Sounds like OP and you mostly agree on this, although you both make the same point in different ways. If everyone is building specific internal libraries, no library is going to take public traction like it used to happen. But yeah I agree with you that now specific internal ad-hoc tooling is much easier to achieve also for small shops than before.
AI becomes godlike and does everything for us.
N years down the road, 3 year old children can just tell AI to generate a custom game or cartoon for them on the spot.
What's left for humans to do?
Live on UBI, explore this wonderful world, colonize other planets..
And along the way, while anyone can make anything they can think of, it'll come down to who has the better idea, we might enter an Economy of Ideas, and maybe the Idea Guys™ will finally have their day :)
As soon as AI can tell original hilarious jokes, I am going to shut my doors and laugh myself to death.
"I was going to tell a time-traveling joke, but you didn't like it." (Hmm, stolen)
I have come to the conclusion that all art that works, have this trait in common.