I understand your point, James. However, I see it like this.
The company designed a product, ostensibly following commonly accepted human user guidelines. When I performed action "X" it acted in a manner I did not expect. That causes me to wonder how the developer expected me to act. Am I using this product in an unexpected sequence? To maximize my benefit from it, should I be using it differently?
If there were no universally accepted rules to software development, then I would agree totally; what you see is what you get, and I need to adapt to using what I have. However, there ARE rules to human interface. If the developer violated them out of expediency, laziness or ignorance then OK, I will learn to patch around it and use what I have been given. But if the accepted rules were being followed during development and I am using it incorrectly, then I deserve to know so that I may maximize the value from my purchase. Thus, I DO need to know "Why?"
