Live data from Hacker News

Coding expertise is going to collapse from AI reliance

larsfaye.com

201–210 of 574 posts

Re: Coding expertise is going to collapse from AI reliance

#201
post #70

I strongly agree with the concept that cognitive friction is the engine of learning. First and foremost, it's an issue of "dependency": if you stop training the "muscle" of logic and reasoning, it gradually atrophies, just like unused physical muscles. You become dependent on external tools that replace a capability you once had yourself. A historical example that brought about a similar shift is this: when the produ…

> Today, having a piece of furniture in our home depends on a massive production and supply chain; the "average" person no longer has the ability to build it themselves.

Tangential, but this is one of many reasons that I (and I suspect many others here) have taken up wood working.

Re: Coding expertise is going to collapse from AI reliance

#202
It appears to be a pattern where I work "expert novice" eventually causes serious incident but is unable to root-cause on their own.

They've become a meat proxy[0] prompting LLM to root cause for them and the ability to fix is capped by LLMs ability, not the engineer's.

I've tried to convince management before this happened and yet here we are.

[0] https://gruhn.me/blog/2026-08-03/

Re: Coding expertise is going to collapse from AI reliance

#203
post #129

Earlier quoted context omitted.

And it's so often wrong that you better be doing sanity checks if you use it for anything.

Is it often flat-out wrong where you live? My most-common frustration with it is when products I want to compare don't have the same quantity-denominator. (Either a different unit, or sometimes a different dimension like weight versus volume.)

I've many times seen it wrong but more often the same item will have some tags expressed on cost per ounce, others per lb, etc. To discourage comparison. But I dont think people are paying much attention to those numbers anyway. Math has become a scary topic for them altogether.

Re: Coding expertise is going to collapse from AI reliance

#204

A list of things, that were supposed to lead to our intellectual demise: - Writing (starting from Platos Phaedrus) - Printed books - Photography - Typewriters, keyboards - Telephones - Recorded music - Television - Wikipedia - GPS navigation - Smartphones - Automation in aviation, medicine, industries

If current trends are anything to go by, who's to say that these aren't stepping stones towards it?

Re: Coding expertise is going to collapse from AI reliance

#205

I often think back to the early GPT days before agents as maybe the last time I will deeply learn a technical subject. I think that was when I actually learned the most as I had to stay completely in the loop. I had recently started a new job and had to work with k8s for the first time. Using GPT to help me implement new services and help me diagnose and fix issues with kubectl taught me so much. Now with agents I do…

The end result is a total and complete reliance on AI providers. It's not really a secret; that's why I started the article with the direct quote from Altman. They would love to see a world where nobody is able to do any type of development work without an LLM subscription enabled...even though they also admit that these models perform best when they are steered by someone who is highly capable and knowledgeable in t…

> Local AI would thwart this vision

While I agree Local AI would be a good goal, even the huge open weight models that can't be run locally are already thwarting the US AI lab's duopoly. Other companies can and do serve up these open weight models, and without having to amortize R&D they are able to serve the tokens at a pretty cheap rate.

Re: Coding expertise is going to collapse from AI reliance

#206

I don’t think there’s a big societal problem here, except that the agentic programming developers may be out of a job like the rest of us. If AI continues improving it will just keep taking over whatever skills are involved in the current AI coding meta are. If it stops improving then the meta will stabilize and after 10 years everyone will have longevity in it. I also see no evidence that AI programming is a difficu…

Depends on what you are programming. I have been using it to build things that have never existed before, that I have wanted for over a decade. Experience gives one more imagination.

Re: Coding expertise is going to collapse from AI reliance

#208

Earlier quoted context omitted.

We've gone through this with chess, and the days when a human can do anything to help AI there are long past; the human can only drag it down. It seems to me to be a form of the bitter lesson. I expect this will happen in every field where we don't add guardrails to require humans in the network. I have a hard time seeing regulation happening around this in the US but vanity may also serve, will CEOs be satisfied rul…

At some point the whims of the CEOs don’t win. The shareholders demand more growth.

Demand from whom, if not the CEO?

Re: Coding expertise is going to collapse from AI reliance

#209
As a tech educator I 100% agree. LLMs are not going to become a "new compiler" where we don't have to worry about the code any more. There's a reason we trust deterministic systems.

I've been worried about this a lot, I even created an agent skill called do-i-understand that's designed for novice devs (and experienced too, because atrophy) where the LLM asks you questions about the PR you're about to submit. I've found it helps a lot: https://github.com/AnthonyPAlicea/skills/blob/main/skills/do...

One way or another, there will be a skill reckoning.

Re: Coding expertise is going to collapse from AI reliance

#210
post #66

Earlier quoted context omitted.

> That sounds great until you realize that "hey Claude, read this Jira ticket and implement the feature in this code base" isn't really worth $200K/year. Nor even €50k/year. Two things are true: 1) The coding part of my career is over. LLMs are capable of doing everything I've ever been paid to *write*. 2) My actual job also included non-coding work: Does this attempted solution even work at all? Is this solving the…

Before, if I would start working / thinking on a problem and discover it was harder than anticipated, that often was a signal that the feature may not be worth it. Because implementing it doesn't fit the current model of how things work or similar. Then it was back to the drawing table and find a better way of solving the underlying issue. But an LLM just happily chugs along and does it, no one feels the friction, wh…

I first brought this up late last year – that there used to exist a kind of selection pressure against both developers and against features which would prevent certain functionality from ever being shipped, specifically:

- Functionality which exceed the technical ability or knowledge of the developer which built it; and

- Functionality which would require an excessive number of changes that time/cost became a constraint (likely because it wasn't an incremental change but a significant rework, or just a bad fit with the existing product).

Sometimes I had the displeasure of joining a company where you could see developers hit these blockers and tried to fight through them (likely under pressure from management) rather than avoid them. And in the process they created a mess of buggy, half-functional spaghetti code which someone else later had to resolve.

Today however, people can use agents to smash through these blockers and ship an incomprehensible amount of crap. And what's worse is they're celebrated by management who don't know any better and see this all as a productivity win with no downside.

I suppose there are two ways to look at this – some would argue that engineers don't need to understand what they're building in detail anymore so non of this matters. Instead they can always use agents to explain what's going on and prompt them to fix any issues that come up.

Then there's another camp which might argue that agents will fundamentally have all the same limitations as humans, and that at some point a codebase will grow too complex that it exceeds even the limits of an agent's knowledge retention or intelligence. Or a codebase may just grow so large that it costs 1 million tokens to make even a simple change.

Unless agents start saying, "there's no way I'm shipping that" like humans used to I don't really see how we avoid the latter scenario... Complexity simply must have limits even if agents allow the bounds of those limits to grow.

At some point models will have to take control or we risk hitting these limits in irrecoverable ways since complexity far exceed that of what a human can reason about well.

If this wasn't true then "build me all the software" would be a reasonable prompt. Because why wouldn't we just get an agent to build everything we could ever possibly need? It's obvious that in the limit there will be limits in knowledge, intelligence and cost.

Whether it's humans or agents, someone needs to manage complexity. That is the most important thing a good SWE used to do. It's why technology selection mattered, it's why good architecture mattered, it's why clean code mattered.

Post reply on HN