Technically, even then doing the same can lead to different results, if nondeterministic events play a role and the different aspects of the software or system may contain bugs. For example mutlithreaded applications where the scheduler can passively influence the outcome of an operation. In one run it fails, in another it doesn’t. A nightmare to debug.
this quote works very well on computers who run instructions pretty consistent.
any larger/ life-level scope and it falls apart from niche cases.
Any software engineer you care to ask will tell you about situations in which doing the same thing has led to vastly different results.
*on deterministic computers.
Technically, even then doing the same can lead to different results, if nondeterministic events play a role and the different aspects of the software or system may contain bugs. For example mutlithreaded applications where the scheduler can passively influence the outcome of an operation. In one run it fails, in another it doesn’t. A nightmare to debug.
yes, thanks for the add!