Earlier quoted context omitted.
anything unpredictable is inherently untrustworthy and requires extra effort to review. Lack of determinism is not a practical concern. it is to me. it's a knockout criteria. it is the only reason that keeps me from using LLMs for coding. nothing else is as serious an issue to me as this. here is why: i tell the LLM to build something with requirements A B C D and E. it builds, i review and i find A B and D are good,…
You'd have to review and verify even changes that you've written by hand. You might think that your hand-written code satisfies A+B+C+D+E, but until you've verified it, you cannot prove it. That's not any different from LLM-assisted writing -- humans are inherently non-deterministic as well :) The other fallacy is assuming that everyone else's experience with LLM-assisted writing is the same as yours. Personally, I'v…
that's irrelevant. my choice can only be based on my experience. i am unable to verify your experience, because i am not you. we have different tolerances, and if it works for your project, then fine.
you just cannot assume that because something doesn't work for you it doesn't work for anyone else.
we are talking about contributions to my project. if LLM coding doesn't work for me, then your LLM created contributions won't work for me either because i won't trust them. you can't legislate or enforce trust. trust can only be earned. lack of trust means i have to spend more effort to verify your code.