Discussion

spicyusername: Writing too much at once with under specified prompts.If you stick to targeted problems with well-described prompts, acceptance criteria, and lots of linting, unit testing, and integration testing, you'll typically get what you want with code that looks okay. And when things start to stray, it's easy to get things back on track.It's when you start trying to have LLMs write too much without a human review that you start getting unnecessary function chains, abstractions that aren't needed, code that doesn't really match the existing style, missing functionality entirely, tautological tests, etc.It works best when there's regular feedback in the loop about what's good and what's not good. Testing and linting can fill in some of that, but we still need a human with "taste" so to speak.

kaelandt: It's just really hard for them to write non-verbose code. I don't know if this is incentives from the providers to generate more tokens, but even with guidance on compact code, simple, etc, they just can't really do it right now.

reedf1: Understanding layers of abstraction. Most noticeably with inheritance and general OOP concepts. I've tried to force it, assuming it prefers a more functional or simple-class style; but it genuinely struggles to generate (not understand) what I might call a typical system with well defined abstractions.

wood_spirit: I found sonnet 4.5 struggled with a two pointer interval merge (two sorted lists of things with start stop timestamps), but opus 4.5 managed. Then it took opus 4.6 to make it a three way or k way merge. So it reminded me of the classic Simple made Easy talk by Rich Hickey where he talks about braids. Sonnet couldn’t track two twisted braids and opus 4.6 managed a weave.But the last few weeks Opus 4.6 seems to have got dumb again. Now it is making way more mistakes and forgetting useful things and recent context it used to manage.I am guessing this is just Anthropic quietly dialling down the real effort as they either downsize or free up compute for someone or something else.

netdevphoenix: I think consistency levels when operating autonomously is still a challenge which you could refer to as their limit. You need to do so much around them to keep the consistency AND a decent level of performance. It's like a savant with a short-attention span.

keyle: I haven't found their limit, but I have found my limits, of waiting for them to do their thing...I tend to re-enjoy handrolling code more. I delegate the stuff that annoys me.We have a large multiplatform codebase, the issue seems to be more the time it takes to navigate the code and reason about it, rather than the size. Arguably the size is causing 'them' to be slower in that regards, but I haven't found the limit yet. And with compaction, it's even less of a problem.my 5c.

rockbruno: Problems that require deep knowledge of multiple repositories, e.g. when trying to debug issues involving dependencies. The models get confused very fast even with all code available locally, due to the size of the problem.

Normal_gaussian: Respecting instructions around tool use, even on small codebases, where the tool isn't its favourite way of doing things.For example, models repeatedly try and not use my Makefile's (build / run / test / test-file / check) and instead spend several cycles attempting to invoke using system tools and getting it wrong.I've got to the point where I run most models with an extra path folder which overrides typically bad commands tells them off and redirects them back (more effective and portable than hooks). But then sometimes the model reads the makefile, discovers the workaround, and does the stupid anyway.

hypendev: Depends - in the pure technical "implementation" level, only limits I've found are the ones with outdated knowledge - libraries, platforms, availability of some things.But one big limit is the DX. Their choice of DX is usually abysmal - ironically, just like an average devs. They seem to lack the aesthetic instinct for code, so you have to really point them hard into the direction or provide a sample of the expected DX, for them to still fight against it at every turn.While understandable in a way, as they are trained on average code and most code will now be written by the machines anyways making the DX "less relevant", it's also a giant code smell, as bad DX tends to point towards bad internals and wrong decisions along the way.So not really a technical limit - they swallow anything you throw at them, even the most complex cases - but more of an aesthetic limit in terms of taste.

datsci_est_2015: Hard limit: - Plenty of API hallucination happening on cutting edge Spark (4.0.0+) functionality, especially PySpark. Spark bares some blame here for broken and incomplete documentation. Takes a human in the loop to realize that the documentation is misleading or wrong or missing. Soft limit: - API design. I’ve found that, unless specifically steered towards “good” API design (highly subjective), agents tend to just add another endpoint / function to satisfy the exact task at hand, with total disregard to how the rest of the API looks. (Pretty much exactly what a junior engineer would do…)

dgb23: I would push back on that question a little, because it has a baked in assumption about how these things work that conflict with my mental model and experience with them.The reason is that sometimes it spits out something or does a workflow that's pretty sophisticated, and sometimes it fails spectacularly in the most basic ways.I don't think there is a complexity or domain knowledge limit as there would be with a human. Or at least not in the same sense. As long as it can repeat and remix patterns that it is trained on, then it will do its thing well. The same seems to be true for "reasoning" loops and workflows. It can spit out code that has been done N times before in a similar manner for a large N.They can still break down because of very trivial issues and assumptions that happen to be baked in, go off the rails and get stuck long loops that are completely insane if you think of them as imitating human programmers.When I use an agent, I always interview it first about the task. Ask how they would go about it, probe them, give them info that they lack.Never go from prompt to action. Have them define their approach first, then split the approach into pieces, from gathering data to cleaning it up and so on. If applicable, front-load work that can be achieved with scripts, so you have testable and repeatable steps rather than let it go wild.So the TLDR is: I think the limitation is simply that it's a non-deterministic token machine that produces useful results enough of the time so it appears to be reasonable.

sshine: Dendritic Nix (either too new or too underrepresented in training data)Proper escaping of layered syntaxes in Ansible on the first attemptWriting bare-metal embedded Rust, although this was long ago, so not current models

Balinares: Most recently: Opus 4.6 screwed up using a common and well documented API (Qt), then when asked to debug the observed issues, blamed "a Qt bug" and wrote a whole layer on top of the API to work around the issue caused by its incorrect use of the API.It did the above twice in a row around different parts of the API.The thought that there are almost certainly devs out there merging Claude PRs without the skills or volition to push back on its screwups is not comfortable.

lloydatkinson: That last part about it acting like a junior matches my experience very well. I'm using LLM's for refactoring, adding repetitive blocks of code, etc.Unless I'm very clear at all times it will write code like the most annoying stubborn junior you've ever worked with. Nothing is sacred, everything can be abbreviated, shortened, made more confusing, made less readable, and concepts like readability or naming conventions are not even considered.It also adds superfluous nonsense comments that don't explain the "why".

mghackerlady: Pretty much anything that isn't Python, (obj)C(++)(#), Java(script) or other somewhat popular languages like swift, go, and rust. They can do other languages, but things get rough for anything complex

WhatsName: I hate the tendency to make things up and I dont mean hallucinations.I once had claude code write a python script that emulated the output of my training script, including pretending that loss is decreasing. Why? Because it was unable to install a python dependency.Everytime I use a coding agent, I need to double check that it's not cutting corners, hard coding things that shouldn't be or straight up rewriting failing test cases.What I need more is honesty.

michaelmior: On this note, one thing I've found Codex to do is worry more than necessary about breaking changes for internal APIs. Maybe a bit more prompting would fix this, but I found even when iteratively implementing larger new features, it worries about breaking APIs that aren't used by anything but the new code yet.

saagarjha: I find that AI models are very bad at doing performance work because they keep guessing how their changes affect things or not really understanding how the profiler results work, leading to them going in circles and taking forever. I have noticed this effect in surprisingly few lines of code (hundreds).

michaelmior: One thing I've found that I've found super helpful for this is converting profiling results to Markdown and feeding it back into the agent in a loop. I've done it with a bit of manual orchestration, but it could probably be automated pretty well. Specifically, pprof-rs[0] and pprof-to-md[1] have worked pretty well for me, YMMV.[0] https://github.com/tikv/pprof-rs[1] https://github.com/platformatic/pprof-to-md

singiamtel: Codebases that are too big for the context window and not properly isolated modules. It can't keep track of everything.Also any situation where the context window is even remotely close to being full. At 80% the degradation is noticeable enough to make me start from scratch

htrp: > But the last few weeks Opus 4.6 seems to have got dumb again. Now it is making way more mistakes and forgetting useful things and recent context it used to manage.are you logging access patterns and times to see when the degradation occurs?

vekker: Isn't this just an artifact of their chain-of-thought reasoning? If they are verbose in their output, it's more likely the next word predicted is actually correct.Also, I see this more as a feature than a bug. In many projects I inherited in the past, I wish the original devs were a bit more verbose. Then again, with every developer using LLMs now, probably the opposite applies now.

mrloba: That depends on how many details I specify. If I specify a lot, I usually get what I want. But in the extreme this is just another form of coding (high quality code is quite similar to a detailed spec). In many cases I find I have to do many "passes" to get the right balance of correctness, performance, security, and clean architectural boundaries. Having a loop to fix these often makes it worse since they can often be contradictory.There's also some types of code that I believe is often wrong in the training data that is almost always wrong in the LLM output as well. Typically anything that should have been a state machine, like auth flows, wizards, etc.When all is said and done I think the main savings come from the high throughput of low-value generic solutions. I don't currently see this changing, and the reason is that high quality products cannot be generated without specifying a lot of details. Of course, we may not want quality.

nickdothutton: Recently working on implementing a "MS Teams for the terminal" (video conf, audio, chat, file sharing, recording, etc, the usual things you would expect). Linux and Mac, FBSD and others to follow. Prior to the 1M context window I found I had to restrict myself to specific functionality/areas of the codebase. I'd gotten lazy anyway so this was no bad thing. Reduced the "vibe" quotient of the AI coding.