| ▲ | rstuart4133 2 days ago | |
You are equating n LLM's output with FORTRAN? The only time you really need to look at core dumps of a FORTRAN compiler is when you think the compiler has a bug. Apart from that, the abstraction doesn't leak. You don't need to know any details of the CPU to debug what is going on, every compilation you do is deterministic and has a predictable outcome. When you make a change, you should be able to predict the exact outcome. Don't like it? Reverse the change, and you're exactly where you were before. I've coded on a few machines I've never bother to learn what the metal does. It is always like this, and it's fine. LLMs are nothing like that. Like FORTRAN the LLMs make you feel like they've abstracted you from the code. But you can't get by exclusively feeding instructions to an LLM. The OP made was making that point when he said "When AI can’t solve it, they just keep trying and failing". When your only undo is to say "fix the mess you just created", you can't replay instructions you gave yesterday to give you the same result, and you can't even say "explain what you did" and expect to get a reliable answer, there is no out. You have to look at the code. When the abstractions leak badly, you have to learn both the abstraction and the thing it's trying to simplify. They are little better than macros that save you typing. An LLM is a very leaky abstraction. | ||