In fact, I think this is a good example of needing to fully understand all use cases of a particular feature before making judgements on its usefulness. An integral part of working on a system is fully understanding the needs of all of the users, needs that may not have been intended during the primary design of the system.
I know I've fallen in to this trap before, where I've proposed a design change to a system and had a prototype manufactured only to have the workshop floor staff immediately explain why it's useless, because it cannot reproduce some unintended but now-important function of the original design.
Conversely, it's also good to look at unintended uses of previous designs. I've used equipment for functions it was never designed to do, but nevertheless proved to be a simple and effective solution.
Comments
In fact, I think this is a good example of needing to fully understand all use cases of a particular feature before making judgements on its usefulness. An integral part of working on a system is fully understanding the needs of all of the users, needs that may not have been intended during the primary design of the system.
I know I've fallen in to this trap before, where I've proposed a design change to a system and had a prototype manufactured only to have the workshop floor staff immediately explain why it's useless, because it cannot reproduce some unintended but now-important function of the original design.
Conversely, it's also good to look at unintended uses of previous designs. I've used equipment for functions it was never designed to do, but nevertheless proved to be a simple and effective solution.