Live data from Hacker News

Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

arxiv.org

101–110 of 230 posts

Re: Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

#101

I'm a convert. I was 100% skeptical about LLM code generation, now over 80% of the professional code I write is generated. That said, the limitations are kind of obvious and are starting to show in some of my projects, and this article seems to confirm my suspicions. If it's just confirmation bias or not, I can't say yet. In my experience, for anything complex enough, I have to start adding more and more constraints,…

[flagged]

Re: Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

#102
post #13

Earlier quoted context omitted.

To this day frontier models think that A and not B means A and B when the sentence gets pushed far enough back in their context window. The context length that model can reason over without obvious errors is much smaller than the advertised context. Between a 1/4th to a 1/20th what is advertised on the tin.

Do you also happen to remember what you ate last thrusday?

Do you have a point? Because last time I checked, AIs were supposed to be better than us fragile faulty humans, and weren't designed to emulate us and all our faults.

Re: Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

#103
post #90

Earlier quoted context omitted.

It means having taste. People say Picasso was a great painter, but that cannot be verified (at least, not in the sense of a verified reward).

"people say picasso was a great painter" is definitely not hard to verify . lol.

I don't know if you're being factitious or not but that was not what I meant. Picasso being a great painter is an example of "having taste"; "create an artistic image generation model with Picasso-level performance" is a valid problem statement we could attack with RLHF, but not with RLVR, because "taste" is not amenable to modeling with a reward function.

"Write this code in a way that is readable and maintainable" is another example.

Re: Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

#104
post #100

Earlier quoted context omitted.

Oldheads remember when GPT 5.2 was at the forefront of agentic programming. December 2025 feels like eons ago, but alack it was an entire half year!

If I'm not using got 5.5 high reasoning I'm wasting time.

Well, maybe so, but how did you feel about 5.2 when it was OpenAI's frontier model? That's what I'm getting at – it was the equivalent of your gpt 5.5 high reasoning just six months ago.

Re: Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

#105

Earlier quoted context omitted.

If it’s not easily verifiable, LLMs aren’t good at it.

but what does it mean to be good at something that cant be verified. how do you know that they are not good at it, you are obviously using some measure. sounds like an oxymoron of a claim.

You just threw the "easily" away from the comment you are replying.

Re: Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

#108

Earlier quoted context omitted.

"people say picasso was a great painter" is definitely not hard to verify . lol.

I don't know if you're being factitious or not but that was not what I meant. Picasso being a great painter is an example of "having taste"; "create an artistic image generation model with Picasso-level performance" is a valid problem statement we could attack with RLHF, but not with RLVR, because "taste" is not amenable to modeling with a reward function. "Write this code in a way that is readable and maintainable"…

https://futurism.com/artificial-intelligence/real-monet-ai-c...

Re: Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

#109

Earlier quoted context omitted.

but what does it mean to be good at something that cant be verified. how do you know that they are not good at it, you are obviously using some measure. sounds like an oxymoron of a claim.

You just threw the "easily" away from the comment you are replying.

doesnt make a difference to my comment

Re: Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

#110

I'm a convert. I was 100% skeptical about LLM code generation, now over 80% of the professional code I write is generated. That said, the limitations are kind of obvious and are starting to show in some of my projects, and this article seems to confirm my suspicions. If it's just confirmation bias or not, I can't say yet. In my experience, for anything complex enough, I have to start adding more and more constraints,…

[flagged]
Post reply on HN