(no title)
pyrale | 17 days ago
The absence of means to measure outcomes of these prompt documents makes me feel like the profession is regressing further into cargo culting.
pyrale | 17 days ago
The absence of means to measure outcomes of these prompt documents makes me feel like the profession is regressing further into cargo culting.
bandrami|17 days ago
1. Reproducibility
2. Chain of custody/SBOM
3. Verification of artifacts of CI
All three of which are not simply difficult but in fact by nature impossible when using an LLM
EdNutting|17 days ago
unknown|17 days ago
[deleted]
XenophileJKO|17 days ago
pyrale|17 days ago
When my code compiles in the evening, it also compiles the next morning. When my code stops compiling, usually I can track the issue in the way my build changed.
Sure, my laptop may die while I'm working and so the second compilation may not end because of that, but that's not really comparable to a LLM giving me three different answers when given the same prompt three times. Saying that nothing is deterministic buries the distinction between these two behaviours.
Deterministic tools is something the developper community has worked very hard for in the past, and it's sad to see a new tool giving none of it.
latexr|17 days ago
https://rationalwiki.org/wiki/Deepity
Determinism concerns itself with the predictability of the future from past and present states. If nothing were deterministic, you wouldn’t be able to set your clock or plan when to sow and when to harvest. You wouldn’t be able to drive a car or rest a glass on a table. You wouldn’t be able to type the exact same code today and tomorrow and trust it to compile identically. The only reason you can debug code is determinism, it is because you can make a prediction of what should happen and by inspecting what did happen you can can deduce what went wrong several steps before.