Developers all over the world are under pressure to use these improbability machines.
Or for manufacturing automation, take a look at automobile safety recalls. Many of those can be traced back to automated processes that were somewhat stochastic and not fully deterministic.
Yes, it is hard for customers to understand the determinism behind some software behaviour, but they can still do it. I've figured out a couple of problems with software I was using without source or tools (yes, some involved concurrency). Yes, it is impractical because I was helped with my 20+ years of experience building software.
Any hardware fault might be unexpected, but software behaviour is pretty deterministic: even bit flips are explained, and that's probably the closest to "impossible" that we've got.
Even better: teach them how to develop.