I see both sides of the argument people endless have over this. I have been hesitant to take a solid position, first because I suck at coding and second because I dont really have a dog in this fight.
The only context I have is my friend in HVAC from many years ago that went to a school that taught everything manually because they wanted people to have a deep understanding of it. What happens to code in the future when people don't have a deep understanding?
I love monkey-patching some python or js. But never have I ever suggested that anyone would should do it. Writing everything in Haskell sounds lovely but I wouldn't advise that either.
I honestly don't care what language I'm writing in. LLMs bring us back to the smalltalk days: your code is data and your data is code. LLMs bring a translation layer so that even if you're writing some high-level language, some DSL that exists only on some 1-off platform that no one else is aware of, _everybody_ has access to a self-bootstrapping codebase.
I feel more empowered to _code_ than ever: now, every single input carries semantic weight that gets carried through the "compiler." Every claim of determinism can much more easily be fuzz-tested and made more robust. "'sup, this broke, fix yo" and "Would you be so kind as to fix this error?" contain semantic context that actually affects the output of the generated code. That restores empowerment around code _authorship_ while still preserving the guarantees we want from the published artifact.
"Deep understanding" doesn't disappear when you gain the ability to be more expressive. "Deep understanding" disappears when people become incurious.
But most of the time coding is a means to an end. I bet your friend in HVAC was not told to use a manual drill to have a deeper understanding of how to make holes for installation. AI is simply a power tool.
I could not disagree more strongly
Using a power tool does not erode your ability to think about how to build a shelf.
Using AI to write for you absolutely erodes your ability to think about what you're writing, be it software or blog posts
Personally I would never use AI for writing, but it's absolutely a power tool for coding. I still need to think about what needs to be generated, and why. For now, I still need to guide the model based on my experience. And in the end, I'm on the hook to approve what's created. If anything, I have more time to think about what I'm making, because I'm not busy building the CRUD for a web app for the 100th time.
Do you think it is a coincidence that literacy rates among the younger generations are lower than previous generations right now?
Imagine making the same argument for text to speech. "You don't need to learn how to read or write because you'll always have a voice activated AI assistant to read stuff for you"
Maybe that doesn't bother you. I think it would represent a horrifying backslide of society into ignorance
> Do you not enjoy coding? I'm not trying to be snarky, just a genuine question
To follow this debate through, to maximize coding enjoyment, shouldn't we be avoiding compilers? They take away a lot of the code we need to write. Frameworks as well?
Aside: there's a clip on YouTube of Linus responding to someone asking if he'd consider using other languages for Linux. His response is that he likes to be close to the metal, and he likes C because you can look at C code and know well enough what the compiled assembly code will look like. You can't really say that with LLMs. You can understand C and you can understand the prompt for building a program in C which will achieve xyz. But you can't actually know what the output of the prompt will look like.
LLMs are categorically a different thing. Instead of soundly translating between formal languages, they adjust how you interact with the formal language.
The enjoyment people get from coding has absolutely nothing to do with the pure volume of code they produce, to the point that this has long been a cliche!
Yeah, equating LLMs with compilers is sloppy thinking (though, I'm sure some sloppy thinkers will defend to death). It's an over-eager pattern match, not everything that takes input and produces output is the same kind of thing.
I bet in our new AI utopia, we'll get more sloppy thinking. All kinds of people will be talking about how they used to think, but now they "no longer have to do it."
The pleasure comes from the "the only right lines of code" instead of "the most lines of code".
There is no excuse for lazy execution using AI, that is, IMO, equivalent to shoddy software engineering. it's just faster and more accessible now. "AI slop" is just poor execution delivered more quickly.
The onus is still on the human in the drivers seat to deliver quality outcomes.
And before you post the obvious response, no, if you're truly "100x faster", you're not reading or even thinking about anything the AI is outputting. The time math doesn't add up.
Surely at some point you would stop saying "I built this house", even if you ordered and financed it?
So I go from typing to prompting and reviewing diffs.
There is no way I install an agent on my laptop so I stick to web UI
Just because everyone is profitmaxxing anthropic by running all the agents, I don't have to.
For me, it is not about the syntax nor the mechanics of typing though. My enjoyment comes from thinking about problems and breaking them down, or thinking about what architecture would best serve them. I guess I'm meant to be a systems design guy, so I'm lucky that AI-coding fits this well (AI models have limited context windows, relative to the size of codebases, so doing the big picture thinking is still important, and fun for me).
I pretty strongly think it doesn't resemble coding even a little
What happen is that their boss gets a 3 page email screed with pictures of how they fucked up the thermostat wiring in trying to gerry-rig a new heat pump/air handler that supports only electric resistance backup heat into my house which has an oil boiler for backup. And I get shit from my wife about why our $10k new heat pump is blowing cold air on her during defrost cycles.
Like honestly I’m losing my mind, when people claim I haven’t written code in a year. You had the wrong job your whole life and whilst you think you are so frontier now by using agenst your market value is actually decreasing.
Imagine a painter saying, I’m so happy I don’t have to paint anymore. Or a tennis player. I’m so happay that I don’t have to play tennis anymore.
wtf is going on?
I don't think my job was ever to type fast, nor do I make any claim that I'm ontologically better than someone writing code by hand - but for what I need to do, I'm way faster now.
You might think he's an AI shill, but I was pretty compelled by simonw's post and idea - "your job is to deliver code that works" [1]. I think I can deliver more code that I can prove to work, faster now. The productivity is nice, but as I've said on other parts of the thread, it's also just fun to spend more time thinking, less time hitting the semicolon on my keyboard?
[1]: https://simonwillison.net/2025/Dec/18/code-proven-to-work/
Edit: should have used [1] in the first place instead of an asterisk.
Most changes I need to do are few lines of codes or big architectural changes. I’m at 40k lines of code after 24 months of working that’s 1.5k lines per month and 50 lines a day. If you can write 50 lines a day would you let AI write those or write them yourself.
I challenge anyone to show me a project with a good codebase where the actual loc output is so high that a human couldn’t write it in one hour a day.
I’m not working for a company so my job is to deliver a platform that works for users not to get a paycheck.
Also the jury's out on if they're losing market value. We have yet to see which way the wind blows, but I personally think the genie might be out of the bottle on this one.
Full disclosure: I'm personally working up the courage to quit, take a fat paycut (maybe) and do something bucholic with the rest of my working life. I don't find much enjoyment in the tech landscape anymore (I'm 37).
If i want to have a script that does sth trivial I’m happy to let AI do it, but if I’m building a house that doesnt break hell no.
There is no way your hands can produce code faster than a machine.
Even before AI, I used a custom code generator for years. It generated about 90% of the code needed for large business applications in seconds, including support for multiple protocols, database adapters (Oracle, SQLite, in-memory, etc.), and programming languages such as C++, TypeScript, and Java.
Writing the same amount of code by hand would have taken even the fastest developer months. The machine did it in seconds, and it did it consistently and bug free.
We all become knowledge experts especially when the data we see inside our glasses is always 100% correct. This could take Years but that's where we are heading and Im sure no one now likes the sound of it.
However, I love putting something in front of users, seeing them use it and get value out of it. And AI lets me get there 10x faster.
It's a really personal thing; some of what you like can be getting some kinds of results quickly, for example. The answer to "What is it like to code?" or "What do you like about coding?" cannot be overly generalized or reductionist since it depends as much on personal preferences as it does classifying activities.
Sometimes, I will review every line, test the front-end in a staging environment, verify the backend contract, et cetera. Over time, though, I realized that many of these reviews just didn't result in any necessary changes. The current model (with guidance/claude.md/etc) was able to one-shot the task.
Not to overly personify, but imagine how you might treat a junior colleague. You start by reviewing everything they do with a microscope, later you review the broad-strokes, and eventually, for low-stakes or well-scoped tasks, you just play with the demo and the ticket and approve it.
Otherwise it's not materially different than a pre-AI world - you've got sample I/O, test cases, hand-review, look at the application on different screen sizes, contrive some edge cases, test against a spec if there is one - et cetera.
But without formal verification and a human reviewing specifications to ensure alignment, I think code will end up being broken in unexpected ways or drift away from the original intent.
Companies are paying for software, not for owning the code.
And frontier models routinely crush all the above in a way I couldn't, at speeds unattainable to mere flesh and blood like me.
People making end-user applications might think they can tolerate more errors and bloat from AI.
Just because they can get away with doing that with AI (and that's debatable) does not mean that people can also get away with that in developing tools, libraries, languages etc. The errors, bloat and instability bubbles up exponentially as people build on it.
There seems to be this fallacy of "I don't have to write code anymore, therefore nobody will have to write code anymore."
I see a lot more of "AI coding doesn't work well in this specific case, therefore it's entirely useless".
Library-type work has mostly been side/toy projects, although fwiw, with a standard/spec on hand (CommonMark for example), I'm also happy w/ the output. It's often possible to "close the loop" and have the coding agent autonomously iterate until the standard is adhered to.
Creating something that is solid enough for widespread, reliable building is just in another category. And I wish people recognized this distinction more when they say we don't need to look at code anymore.
That said - I would (again, maybe naively) suppose it's not hugely different - much of the work I do occurs in code where many people have and will work on it, and where the size of the codebase dwarfs model context windows.
In that case, I feel the same - current frontier models, when properly oriented to a task, with some assist on the big-picture thinking - are more than capable of generating good code that can slot into big codebases with many moving pieces. Of course, I'd have to point to other people's work to defend this, but I think that's still pretty reasonable especially against the declared "LLMs are worse than useless for generating code".
> It is nearly inconceivable to me that I would ever go back to writing code by hand, in any context.
In any context? Sorry but they aren't that good yet. There are definitely areas where they are going to struggle. Maybe fewer than before. Maybe you can say "in any context where a junior-to-mid programmer would be ok", which I would agree with.
> If you use AI for anything else, and in particularly if you use it to generate code, you're wasting your time.
Have not used frontier models in at least a year.
It is nearly inconceivable to me that I would ever go back to writing code by hand, in any context. Even if no new model was ever released, the combination of GLM 5.2 and DeepSeek V4 flash is more than sufficient to do real work. It's not hard to imagine that a distillation of Mythos/5.6S or whatever is a couple generations away will push me even further in this direction.