Even driving a 5W tube amp to distortion is ear shattering loud. I don't even know how people can do that to 50W tube amps.
They stand farther away from the speakers than you do
I agree with you completely about cross platform development being one of the best methods of exposing bugs, but i don't think this kind of stack randomization is really comparable. When doing cross-platform development, you'll have a very specific, very well-defined set of target environments that you'll be testing a single version of software on. This stack randomization is an effectively infinite number of variations on a theme being tested in a single environment. One lends itself to repeatable testing, the other lends itself to versioning hell trying to replicate bugs in order to solve them.
I agree it's worth looking into, but I'm currently having difficulty seeing how the costs outweigh the benefits.
- What kinds of bugs do you think would manifest earlier using this technique, and why do you think that earlier manifestation of that class of bugs will outweigh the tremendous burden of chasing down all the heisenbugs that only occur on some small percentage of randomized builds?
- How does such an environment reward programmers who invest more time in validation? More time spent in validation will result in better code regardless of whether you're using a randomized or non-randomized build. More time spent in validation is a cost you're paying, not some free thing provided by the randomized build process.
- I don't know what this sentence means: "Debugging suck, if instigated soon enough to matter, returns 100x ROI as compared to debugging code." If what instigated soon enough?
- "Determinism should not be reduced to a crutch for failing to code correctly" - What does this even mean? An algorithm is either deterministic or non-deterministic. If your build system is changing a deterministic algorithm into a non-deterministic algorithm, your build system is broken. If your algorithm was non-deterministic to begin with, a randomized build is not going to make it any easier to track down why the algorithm is not behaving as desired.
All in all, your post reads like a smug "Code better, noob!" while completely ignoring the tremendous extra costs that are going to be necessary to properly test hundreds of thousands of randomized builds for consistency.