Earlier quoted context omitted.
I write code to solve a problem. Not code that looks like it solves the problem if a non-technical client squints at it. And if you don't prove your code, do you not design at all then? Do you never draw state diagrams? Every design is an informal proof of the solution. Rarely I write formal proofs. Most of the time I write down enough for myself to be convinced that the desing solves the problem.
Yes, you can dedicate extra tokens to draw state diagrams, the LLM can actually do that, if you don't have it generating one or more design documents before you are writing code you are doing that wrong. I still don't get how that is different from what humans are doing. > Most of the time I write down enough for myself to be convinced that the desing solves the problem. Again, why do you assume we aren't doing the s…
It was a response to you saying: "Im not going around trying to prove my code correct when I write it manually."
How did you manage to forget what you wrote previously?
Also, in this post you are now suddenly taking the exact opposite position, contradicting your previous point.