|
|
|
|
|
by layer8
482 days ago
|
|
My point is that it is not the same, in a similar sense in which testing (as a software engineering discipline) is not a substitute for proving the correctness of code. Another way in which it is different is that the “coder” cannot test hypotheses of the kind “when I prompt x, then y will happen” other than as a one-off, because that conversion is lossy, whereas in no-code/low-code “when I specify x, then y will happen” is deterministic. In other words, with no-code/low-code, the “coder” can with time learn to predict precisely and reliably what their change will do, which is not really the case with LLM-based coding, where you have to go by the “vibe”. |
|
When it's not, fuck it, go ahead and produce that flight sim without researching quaternions. MOST code does not need to be provably correct, or we'd all use Ada.