That's at least a principled stance, which I can appreciate.

I still disagree, though. It seems like the only logical way to get out of your thought process would be to create software and then never update or change anything. Either that or have every user sign a waiver saying that the product could change in the future and that might impact them psychologically.

After all, why is it different when you're making a change without A/B testing it? Surely every change has some hypothesis attached to it. Does it only matter to you when developers observe the metrics changing?