←back to thread

196 points zmccormick7 | 4 comments | | HN request time: 0.001s | source
Show context
aliljet ◴[] No.45387614[source]
There's a misunderstanding here broadly. Context could be infinite, but the real bottleneck is understanding intent late in a multi-step operation. A human can effectively discard or disregard prior information as the narrow window of focus moves to a new task, LLMs seem incredibly bad at this.

Having more context, but leaving open an inability to effectively focus on the latest task is the real problem.

replies(10): >>45387639 #>>45387672 #>>45387700 #>>45387992 #>>45388228 #>>45388271 #>>45388664 #>>45388965 #>>45389266 #>>45404093 #
neutronicus ◴[] No.45387672[source]
No, I think context itself is still an issue.

Coding agents choke on our big C++ code-base pretty spectacularly if asked to reference large files.

replies(4): >>45387769 #>>45388023 #>>45388024 #>>45388311 #
1. AlGoreRhythm ◴[] No.45388311[source]
Out of curiosity, how would you rate an LLM’s ability to deal with pointers in C++ code?
replies(2): >>45389012 #>>45389408 #
2. neutronicus ◴[] No.45389012[source]
Greenfield project? Claude is fucking great at C++. Almost all aspects of it, really.

Well, not so much the project organization stuff - it wants to stuff everything into one header and has to be browbeaten into keeping implementations out of headers.

But language semantics? It's pretty great at those. And when it screws up it's also really good at interpreting compiler error messages.

3. jdrek1 ◴[] No.45389408[source]
If you have lots of pointers, you're writing C, not C++.
replies(1): >>45389622 #
4. neutronicus ◴[] No.45389622[source]
Eh, it's a big tent