Live data from Hacker News

AI coding is a nightmare. Am I the only one experiencing this?

news.ycombinator.com

51–60 of 62 posts

Re: AI coding is a nightmare. Am I the only one experiencing this?

#51
It isn't a nightmare at all. It's quite incredible if you know how to do it.

I haven't written any code since November. People getting bad results don't know what they're doing.

A way to tell if you're doing it wrong is if you're writing lots of prompts. That's a huge smell.

Re: AI coding is a nightmare. Am I the only one experiencing this?

#53

Earlier quoted context omitted.

Anthropic did a study where people who worked like this understood their systems a lot better than and were basically as fast as AI maximalists. Plus it’s so much cheaper… that has to matter.

Wait, hold on. So you're telling me that Anthropic is out there hyping their newest, most powerful LLM like crazy... but really it's just a token-selling scheme?

Pretty sure their strategy is "hype it up, stuff it down EVERYONE's throat, once everyone is hooked and the tool is indispensable, make them pay for it. And rachet up the prices every quarter".

Re: AI coding is a nightmare. Am I the only one experiencing this?

#54
post #31

Earlier quoted context omitted.

>Problem 3: "you'll hit the 200k token limit..." ... Suggestion: use 1 million context window LLMs. Yes, if the model someone is using only has 200k token limit, that would immediately suggest to me that it really isn't a sophisticated enough model. Most of my coding sessions end up being about 350k tokens long when I finish, it wouldn't even fit in a 200k context. And that isn't counting the cache-reads by subagents…

minimax m3 has a 1M token context window so not sure how op is hitting this 200k. maybe the plan they're on? or some setting in some layer of whatever their dev tooling is using.

I did a quick look for 200k models on OpenRouter. There's a lot of previous-gen Minimax 2.5 & 2.7, GLM 5.1 that are around 200k.

But also on the list at 200k are "Free Models Router" and "Claude Haiku 4.5". I would not recommend making any judgment of AI based on free models. And coding with Haiku is a bad idea... I mean, that was my first code AI test too, but it's just not an accurate impression.

To be fair, Opus 4.1 & 4.5 are also listed as 200k. They did require context management for large & difficult tasks. But if you do have access to Opus, there's very little reason not to switch to 4.8 / Sonnet 1 Million now. I wouldn't recommend Sonnet, but I have used it to write a USB audio driver that got some hardware working on an obscure OS, so it can work.

Re: AI coding is a nightmare. Am I the only one experiencing this?

#55
post #31

Earlier quoted context omitted.

minimax m3 has a 1M token context window so not sure how op is hitting this 200k. maybe the plan they're on? or some setting in some layer of whatever their dev tooling is using.

I did a quick look for 200k models on OpenRouter. There's a lot of previous-gen Minimax 2.5 & 2.7, GLM 5.1 that are around 200k. But also on the list at 200k are "Free Models Router" and "Claude Haiku 4.5". I would not recommend making any judgment of AI based on free models. And coding with Haiku is a bad idea... I mean, that was my first code AI test too, but it's just not an accurate impression. To be fair, Opus 4…

you're right, i remember pre 4.6 i believe 200k was the norm.

Re: AI coding is a nightmare. Am I the only one experiencing this?

#57

So stop. I’m serious. Treat it like any other tool. When it helps solves problems, use it. When it makes problems, don’t use it. There are a lot of people and an enormous amount of money trying to make hands off agentic happen, but the happiest and most effective enthusiasts I know do not give up control: they go function by function and class by class, generating or writing as they see fit. The goal is to make usefu…

The problem with this affects professional coders more than hobby coders. Many jobs are pressuring their developers to use AI tools under threat of termination. Yeah, if you're coding on your free time, you can easily avoid AI. But many corporations have swallowed the AI Kool-Aid and actually require their devs to use AI tools.

The goal, to corporations, has never been to "make useful software". The true goal is "make software that will bring us a revenue stream". If they think they can use AI to do that faster with less human payment, then they'll snap at it. AI doesn't ask for its rights (because it's not AGI, so it doesn't have actual rights). AI just tries to do what its told, and fucks up at doing so at a higher rate than the average human. But corps think it'll be cheaper so they swallow the tales told to them by AI executives who have a highly vested interest in making sure you use their AIaaS.

Hobby coders are coding for the fun of it, and aren't going to use AI to code. They might use AI to help them understand the subject matter better, but the code that hobby coders write is highly unlikely to be AI vibecoded. Evidence: I severely doubt that any demosceners will ever use AI to write the actual demo code.

Re: AI coding is a nightmare. Am I the only one experiencing this?

#58
Genuinely experiencing it daily and tackling it by having a few audit agents running in parallel to keep the big picture and feed context as needed. However, this is terribly expensive.

My question tho is, how confident are we about an agentic future? I mean coding was the one thing agents "are best at". How would you run a complex system/organization on an agent where they will need to face with a massive (and growing) context through a limited context window?

Re: AI coding is a nightmare. Am I the only one experiencing this?

#59
These problems come from giving LLMs too much agency. The fix is to ruthlessly manage context yourself, and use a harness that only allows one LLM response at a time. Don't leave context up to the LLM, and check everything it is doing. This gives you most of the speed increase while still giving you clean, concise, human-reviewed code.

Re: AI coding is a nightmare. Am I the only one experiencing this?

#60
You're not. Most of the pain you're describing is the model not knowing anything your team knows. It doesn't know you already tried that approach in March and it broke billing. Until you feed it that history it will keep confidently repeating your old mistakes at higher speed.
Post reply on HN