Comment by sarchertech
17 days ago
Well if you want to use it as a high level language where you check in the spec and regenerate the code then prompt instability/chaotic output makes that infeasible.
You can’t just tell users “sorry there are a million tiny differences all over the app every time we change the slightest thing, that’s just the ambiguous nature of reality”.
>where you check in the spec and regenerate the code then prompt instability/chaotic output makes that infeasible
What, why would you want to write the code anew? Identify the changes in the spec and bring the existing code in line with them.
That’s the whole thesis of the article. Using an LLM as a high level language.
>The codebase should be reconstructable from the documentation
And this kind of reproducibility is insensitive to prompt instability. If your inference is deterministic (trivial if within the lifetime of a snapshot), you give it the same docs and get the same result.
1 reply →