Trying to understand where you might be going with this. Is the implication that non-deterministic/stochastic algorithms have no practical use in engineering?
No, they have a place where stochastic algorithms are necessary. For writing a hello world application, no stochastic algorithm is necessary. Comparing compilers with LLMs is comparing apples with oranges.
I think it will become more apparent over time. But consider that the practice of software engineering is a stochastic process. Give 10 different engineers the same goal, and you’ll get 10 different solutions.
If a SW dev applicant gives a 20-file generated output for a 20-line assessment problem and can’t explain single lines of “their” code, either what they should be doing or why “they” had written it, it’s gonna be a no from me, dawg. A standard problem might have different solutions, but fixing the issue of the day to the satisfaction of a rabidly vocal customer base might have one at most, and it will change multiple times on a whim.
So the LLM might have helped them cheat their way to an MSc, but there’s no cheating your way through real life.
Trying to understand where you might be going with this. Is the implication that non-deterministic/stochastic algorithms have no practical use in engineering?
No, they have a place where stochastic algorithms are necessary. For writing a hello world application, no stochastic algorithm is necessary. Comparing compilers with LLMs is comparing apples with oranges.
I think it will become more apparent over time. But consider that the practice of software engineering is a stochastic process. Give 10 different engineers the same goal, and you’ll get 10 different solutions.
At that rate me walking to the store is stochastic because a grand piano could fall on my head. We have to draw the line at some logical point.
What line are we trying to draw exactly? I think that’s the part I’m still confused on.
Yes, walking to the store is a stochastic process. Ask anyone working at google maps.
I think you’re arguing for arguing’s sake. If you don’t see the point by now, then I am unable to make it more clear. I’m sorry.
If a SW dev applicant gives a 20-file generated output for a 20-line assessment problem and can’t explain single lines of “their” code, either what they should be doing or why “they” had written it, it’s gonna be a no from me, dawg. A standard problem might have different solutions, but fixing the issue of the day to the satisfaction of a rabidly vocal customer base might have one at most, and it will change multiple times on a whim.
So the LLM might have helped them cheat their way to an MSc, but there’s no cheating your way through real life.
What you’re describing is “vibe coding”. For the difference between vibe coding and engineering, I’ll refer you to my previous comment.