Why are you so concerned about the LLM producing the exact same code across different sessions? Seems like a really weird thing to focus on. Why aren't you focused on things like security, maintainability, UI/UX, performance?
Why are you so concerned about the LLM producing the exact same code across different sessions? Seems like a really weird thing to focus on. Why aren't you focused on things like security, maintainability, UI/UX, performance?
Agreed. It's not like humans can produce the same output given the same input for anything more than trivial inputs.
I'd argue that it's actually a benefit; I like that I can do several generations and compare them and pick the best result. HP, for example, used to do this with software teams, and that's how we got Rocky Mountain BASIC (AIUI the competing team was East Coast BASIC).
Comp-sci people like repeatability when they want that and true randomness when that is desired. Things in between are rarely desired.
In computing, things are much more useful when they behave in predictable ways. Even AI, many (most?) would argue.
Computer science and software development are hardly related
Check the Plan9/9front papers or IWP's and say that again after reading the docs on GeFS for instance.
Thanks you proved my point
You are wrong. You may think that they aren’t related because you write software without thinking about computer science, but that says more about you and modern software development seat-filling than it does anything else.
One can’t write anything efficient without comp-sci being forefront in your mind the entire time you are writing. Which explains exactly why everything is so slow today.
If you’re not thinking about what is computable, what is not computable, and what is easily computable as you think about the problems you are trying to solve, you are a professional novice.
I studied computer science at one of the top colleges. It's true there's a lot of overlap between the two. But they are still very different fields.
You definitely don't need to study computer science just to avoid making common performance issues and in fact just studying computer science doesn't mean that you aren't going to introduce things like N+1 query issues, that's sort of thing comes from experience more than anything.
Likewise, just studying computer science does not mean that you are going to be well suited for software development in the real world.
> If you’re not thinking about what is computable, what is not computable, and what is easily computable as you think about the problems you are trying to solve, you are a professional novice.
Of course I consider all of these things but that didn't come from studying computer science in college lol.