Everyone else needs to start treating them that way, or you're going to regret it once you realize what's actually happening.
A lot of you don't want to hear it but this is a user issue.
I think the world changed. And it's changed for the good. AI is a tool, and we should not be afraid of this tool for the coding world. I am only speaking about coding, I'm not speaking about other uses of AI, just so that we're clear on the scope of what I mean by good change.
For the first time, I see people who had all these ideas finally bring them to reality and watch it blossom. They wanted to build something to share with their communities, but the walls were too high. Too much gatekeeping. Too much of thinking that programming was a task for the elite few and not for the masses. Along the way, we all forgot that we build tools for people. And having an additional tool help us make better tools for people is a win. Just below this comment, I see people talking about dementia, "lots more generated code, almost all of it garbage", "future where garbage software".
I think the only delusional ones are the idea that humans were better at coding. Have you never had to work on an older project? One that you did not have to start fresh on? Or did you come into either one and go "wow, this is perfect! everything is so beautiful!" Do you seriously consider your fresh project (that didn't use AI) to be the best most perfect beautiful code ever?
The fact is that nobody cares. People want to use good things and have fun with their lives. They're not worried about whether you wrote a method that parses some strings beautifully or did it with a one-liner. That never mattered, and I think a lot of you can't let go of that world view change and instead lash out at people who simply embrace that programming was simply a tool, not some elite special skill. And we're going back to those beliefs. It's done. It's over. Get over it.
If you want my attention tonight, surely then "put more effort in" applies here too?
I was a low bar target: I already think AI coding is a mistake. But I want to read about it. Not listen to it with megabits of associated video I don't want to watch either.
Tag as "rage bait" and move on I did not like, I did not subscribe.
1. Internet 2. Smartphone 3. AI coding
All 3 were "WOW" moments for me.
Aspects of coding are faster certainly, but oh gosh can it get very wrong very fast when things go sideways, and with everyone using it, the chaos factor compounds into a near halt.
Do you have any publicly available demonstrations of this claim?
> A lot of you don't want to hear it
That there are skill differences in the use of technology? On the contrary this knowledge makes me suspicious of undocumented claims like yours.
> this is a user issue.
Another claim I wish was quantified. With all the billions invested I assumed this would naturally come to exist. I may have just missed it. Any pointers?
Yeah I mean for example I wrote up a new audio mixer application for TDE using basically claude and just saying - hey rewrite the old ALSA one with Pulse/Pipewire.... its awesome. I dont know how it works.,
Isn't anything else a surrender to irrelevance? I agree that many coding tasks that were previously effort intensive are now not effort intensive, but there's no ceiling I'm aware of on how correct and performant and economical and capable software can be short of saturating the hardware.
And the emergence of agentic intelligence at scale demands new regimes of performance and correctness and economy like maybe nothing else ever has.
I have an anecdote related to TUI flickering in that my TUI library had a flickering problem because it was doing more than 10k FPS, and so I had to lock the buffer swap to the vsync to stop it tearing.
AI coding didn't make more React too cheap to meter, it made notcurses bound into Trinity-inspired deterministic replay event substrate over io_uring possible.
I am in no way surprised a sufficient waterfall method passed to Claude code could result in a completely accurate application. But most applications aren’t built via waterfall for all the reasons.
bitwize•1h ago
Their apparent inability to get the basics right makes me severely doubt their claims of self-improving AI. The humans at Anthropic wouldn't know improvement if it landed on their lap and started twerking, and AI cannot do a job without strong human intervention into what the goals and guardrails actually are.
I'm kind of reminded of when Microsoft claimed it took a team of Ph.D.s to write a terminal application that updated at 60fps, and then Casey Muratori did it over a weekend. And this was before AI was writing code in earnest; when LLM-induced brainrot really sets in, civilization is in for a world of fresh hurt: lots more generated code, almost all of it garbage. And the promised AI crossover point where it becomes AGI, or indistinguishable from for software design purposes, recedes into the infinite future.
wasabinator•1h ago
gdjdhdheb•1h ago
Jblx2•1h ago
SpaceNoodled•1h ago
andrei_says_•1h ago
A true era of ignorance, looking like an ocean of nonsense in which no one can really navigate as it is ungrounded in reality.
Idiocracy presents a naively gentle positive version of such future but there are many darker ones possible.
Kali Yuga, indeed.
https://en.wikipedia.org/wiki/Kali_Yuga
Papazsazsa•39m ago
Retric•20m ago
Remember how they used Brando to water plants and it kills them? Eventually mistakes break critical systems and you fail.
_doctor_love•18m ago
kshri24•6m ago
Kali Yuga lifespan is 432,000 years. Of which we are 4000+ years into it. So that's another 428,000 years of hell on Earth.
ai_slop_hater•1h ago
rvz•1h ago
This is the same Microsoft that is now rewriting the TypeScript type checker, parser and its developer tools in Go after realizing that the bottleneck was...the performance of TypeScript itself, which is a basic compiled vs interpreted difference.
> And this was before AI was writing code in earnest; when LLM-induced brainrot really sets in, civilization is in for a world of fresh hurt: lots more generated code, almost all of it garbage.
Some folks using LLMs wouldn't realize why it makes zero sense to use TS / JS for building performant and optimal applications. This is why people were experiencing significant rendering bugs in terminal apps (they are not designed for that) and slow starts with Claude Code, which was completely vibe coded with Ink.
If you don't understand the basic fundamentals of what you are working on with LLMs and bugs are creeping up left and right, then you are just sinking in your own comprehension debt.
panarky•51m ago
He could have done it in 13 seconds instead of 13 minutes: "Anthropic is lying about the effectiveness of agentic loops because there's this one screen flicker bug in Claude Code that took a year to fix."
Yeah, like when United Airlines claims a plane can fly 300 people 6,000 miles they are lying to you.
I can prove they're lying to you because people have been complaining about uncomfortable seats and flight delays for literally decades and those issues still aren't fixed.
Retric•15m ago
The lie is coding is solved, the proof is they had an outstanding coding issue they were working on for over a year while saying coding is solved. There’s a great number of other issues with their own software that disprove their premise, but you only need one counter example to disprove something.
And because you missed it, the subtext was they want you to use loops not because they work but because they burn lots of tokens thus making them more money.