

Determinism means performing the same way every time it is run with the same inputs. It doesn’t mean it follows your mental model of how it should run. The article you cite talks about aggressive compiler optimizing causing unexpected crashes. Unexpected, not unpredictable. The author found the root cause and addressed it. Nothing there was nondeterministic. It was just not what the developer expected, or personally thought was an appropriate implementation, but it performed the same way every time. I think you keyed on the word “randomly” and missed “seemed to,” which completely changes the meaning of the sentence.
LLMs often act truly nondeterministically. You can create a fresh session and feed it exactly the same prompt and it will produce a different output. This unpredictability is poison for producing a quality product that is maintainable with dynamic LLM code generation in the pipeline.







First, don’t need to respond to arguments made in bad faith. There’s no net positive outcome possible for the other person who is coming to the conversation in good faith.
Second, not having their own solution does not invalidate anything critical they say about the one under discussion. There doesn’t have to be a “better” solution to justify not implementing something that has no positive impact on the targeted problem and severe negative impacts elsewhere.