> In Oct 2026, how many of us don't know this already?

The comments to this article suggest that it's still disputed.

Personally, I think it's a bit of a silly phrase, because it implies an absolute, and all anyone needs to do to disprove it is to show that coding was not solved for problem X. That's still the case -- it's just that the set of X is rapidly shrinking.

I think it's more indicative to say how much you trust LLM code. A little over a year ago, I scrutinised every line carefully, and it was buggy as hell and I had to fix most generated code by hand. Now, models write clean code with fewer bugs (far fewer) than I would. A year ago, I was doing a lot of steering during planning; now, it's rare that I don't agree with the model's first proposed solution, and even if I don't, it's most likely to fix a minor change in understanding, not to propose a substantial architectural change as it was before.

The one thing I'm not sure about is how much this is due to better prompting on my part. I doubt that this contributes much, but I still suspect that continual usage does make you more aware of what works and what does not: how much detail to provide, how to describe a problem or change, how to propose solutions while still leaving other options open.

Find a lot of tech adjacent jobs on reddit and see them talk about being outskilled by new hires using AI to automate sysadmin tasks. I used to a sysadmin very early in my career and given the tools today and the problems back then, a lot of these jobs are going to be obsoleted or dramatically automated to not require FTEs. This is already started in those fields. Powershell and bash scripting is very good from these things and has been for longer than a year IMO.

We're in our own bubbles where a good part of HN population woke up to coding agents being good enough ~1 year ago, there's a group of folks that found out ~6 months before that, and then the people banging their heads on these a bit earlier than that. If you aren't using a coding agent everyday most people are just using these things to apply an instagram filter, or sort a grocery list. Muse is probably the closest thing to 'full automation' a lot of people are seeing for the first time.

Unfortunately I don't think the bubble that exists at the moment is on the promise of automating so much coding as trying to penetrate consumer use cases, which I think are still lacking and not reliable enough yet. As much as I use coding agents every day I still will not let a claw-like near a bank account or a credit card.

I use AI extensively to develop software, but IDK if I would say "coding is solved".

LLMs still mess up a lot if you just let them loose and don't guide what they do.

The structure of the post seems like a comparison of snapshots between a date this year and last. On HN, it's an odd statement. In the context the author is writing in, it seems fair.

If you think coding is solved you dont know how AI applies patterns, or you dont know about coding patterns at all

:raises-hand: I still don't know this. But my definition of "coding" may be different from yours, might it not?

This was Gemini the other day: https://imgur.com/a/7mdqwjk — this wasn't some errant load, even refresh, hard refresh, etc. got the same result for a while. An outage, AFAICT.

While trying to capture that bug, I (ironically) asked Gemini (but the Gemini-via-Google-search Gemini, since Gemini proper was an outage) for the package name of a screen recorder (gtkRecordMyDesktop); the command it returned referenced a non-existent package¹. I then found an alternative, and then hit a bug in that screen recording software that I had to then work around to get the video file there.

The site I uploaded the video to, Imgur, breaks completely — i.e., it cannot even so much as surface an error message — if your browser refuses to let it store god knows what on your disks. (So as it is, I have an extension that says "why yes, of course you can have storage, and essentially provides a black hole. But since it looks like a "success" to the Javascript, the JS doesn't crash!)

This isn't, to me, some one-off interaction. Every interaction with software these days feels like this, more and more. Just breakages everywhere that leaves me wondering if "coding is solved", where is all the bug free software?

(¹forcefully prompting the AI to actually query the package listing netted me a classic "You're absolutely right! The package name I referenced does not exist!")

> In Oct 2026, how many of us don't know this already?

To "know" this, people would have to believe it from their personal experience.

Many people have standards and experiences that differ from yours. Yes, even if they use frontier models.

Coding is solved in the sense that you don NEED to write code anymore. Of course you need to check and design and find better ways of doing things, but nothing of this requires you to write the code directly, you can always design, check and ask the LLM to implement a new version.

I have tons of acquaintances like that. They vibe-code and think they've gained an advantage over those who don't know how to vibe-code But there's nothing to know — take a 3-hour course, pay 200$ a day for Claude, and there you are, a vibe-coder.

It's just that most skilled developers find it disgusting, because the AI spits out code that doesn't work the way it should, and it all turns into the routine of "threw in a prompt, waited, reviewed, repeated." — only those who were crappy programmers are happy about this.

And on top of that, these characters deny the fact that agents are evolving too, and meat proxies will soon be unnecessary — or maybe already are: https://x.com/tunahorse21/status/2117353858544660585

I still don't know. Use Claude and OpenAI all the time, but still manually code, esp regard to setting up modules and data structures.