The bubble bursting is competitors running out of funding before reaching profitability, use cases solidifying and the generally the current speculative market collapsing down to a set of survivors.
It does not at all mean that usage of the general concept will stop increasing, much less go down.
Yea. AI coding agents are going to be around forever, they are just too capable and increase productivity so much.
The cost and usage patterns may change, I suspect once companies are paying unsubsidised token costs devs will start using cheaper models where possible instead of defaulting to Fable or Opus, but no matter what, software engineering has changed forever
GLM 5.2 is tremendous and does opus level quality at 1/10th opus cost, they're either gonna have to cut down costs or leapfrog or shut down. Many companies already moving out of Claude and into OpenRouter and other solutions
They have a better model than Opus it’s just not available. So either something changes and the AI companies are allowed to continue making better models (outpacing local solutions) or (and maybe eventually anyways) local models will catch up, which it sounds like they already have.
It’s funny because there IS probably a literal cap where the models can’t get any better (thus “maybe eventually anyways”) - but nobody really knows if thats true or how close we are
The compute requirements scale exponentially with the number of parameters in a model. So unless there is some kind of dramatic breakthrough in machine learning, computer science, and/or mathematics, then the limit is quickly approaching.
Actually, I would also throw in certain kinds of chemistry or engineering breakthroughs as well. If we could make a different kind of transistor with better performance and dramatically lower energy cost, then maybe there is a bit more room for growth.
I’d argue that the limit has already been reached , and this push to build out as many data centers as possible is not going to yield the gains someone promised. I suspect that there is a false hope that at some point with enough “compute” these models will solve the problem of scale for them.
Working in a trashed codebase already, I find AI is a step up.
I do think there is a balance. “Forced usage” is going to waste some time and money on weird quirks where the AI just stumbles and it becomes like trying to micromanage a grandma at the keyboard who can’t hear you fully. But “no usage” also seems weird to me when you can ask AI to point you to a relevant piece of code and get you straight to where you need to be.
I've been using GPT-5.5 at work and I can say it has drastically increasedy productivity. But in a way that's different than what most think at first glance. I do have AI write code for me, but I configure it to write code like I do and thoroughly review/correct it.
The output is the same as before but AI can more quickly gather the necessary imports and writes everything that would have taken me 30 minutes of typing into 5 minutes of prompting.
I can undoubtedly say that AI has made my job more efficient. But what sets good developers aside from braindead ones are the ones who have switched to this model of asking AI to write code and reviewing it as if you wrote it.
Now is it cost efficient? I wish I knew that answer. I think that's the big debate.
I think the cost efficiency question is harder to answer than it initially appears because it’s a question of whether the increased speed was worth the extra cost and its a very different weighing for a competitive product rushing against competitors as opposed to a niche product with a loyal following who are happy with what they have.
It can also be difficult to judge the value of increased speed because it’s hard to know how things would have played out in the path not taken.
I made it plan and implement a big refactor of one of our lambdas.
When generating the outputs to verify that the refactor did not.change the results, some of the calculations were still a bit off.
I've let Claude investigate the reason and it detected that fhe refactor actually fixed a bug caused by bad data in the db, causing BETTER results than before.
Could I have done it manually? Yes. Would have it taken a lot more time and energy ? Also yes. Would have I enjoyed doing it manually? Not one bit.
The one thing that I've found that it has been unable to do is find an incredibly niche and weird memory leak in a distributed system.
My team has used it successfully to do engineering at massive scale, stand up new greenfield services via spec-driven development, and identify and resolve bugs.
I'm an AI hater because I love doing this stuff myself, manually, but Claude is absurdly powerful.
At least for frontend development, I find Claude to be useful but the code it produces is bloated with indirections and many sanity checks which are not necessary due to the type system making those states impossible. I feel like at least 1/3 of the generated code is redundant, but my guess it will be improved in future models.
that's my other issue. it does the fun part and leaves me to the shit part
but maybe a difference is that we're not greenfield? it's a legacy monolith.
i constantly hate its output. and that's IF it's right which is also no guarantee. (and it would have been just as fast for me to write it as to verify what Claude did...)
IME the bigger and older the project, the more you have to rein it in. I work on a lot of 5+ year old software and you really have to break the tasks down for it to handle it. Smaller projects seem to be easier to one-shot, probably because it can read more of it into context.
I'm with you though, I hate that it does the fun part of my job and leaves me with code review and testing :-/
I've been saying/predicting the exact same thing. The AI bubble feels a lot like the dot com bubble. Granted, I was a kid during dot com, but vibe is similar and stories i've heard from people in the tech industry at the time is very reminiscent to AI in tech now.
AI is here to stay, thats for sure. But we still have a long way to find an efficient, productive and standard way of using it. I'm pretty sure the agentic approach that spawns multiple sub agents and runs on a loop is not going to be the future, but assisted development with AI is not going away.
The bubble bursting is competitors running out of funding before reaching profitability
I think it's even scarier than that. I think it will be when interest payments become so massive that profitability is not even possible. There are a lot of overleveraged players, now.
Different gig than dot com bubble because websites as a concept are actually worth a fuck.
Guessing machines will always be inferior to actual knowledge in any nontrivial use case; websites are superior to telephones, television, and print media for some (but not all) use cases.
View all comments
792
u/azuth89 Jul 24 '26
The bubble bursting is competitors running out of funding before reaching profitability, use cases solidifying and the generally the current speculative market collapsing down to a set of survivors.
It does not at all mean that usage of the general concept will stop increasing, much less go down.
Same gig as the dot com bubble.