My fancy GUI is just too complicated
-
@Anonymouse said:
For example, while we're on the topic of programming some external devices via some interface, imagine that the hardware not only has to be connected properly first, but also needs to be set up into a state ready to receive the programming, like by throwing a switch from the "read-only" position to the "write-enabled" position first, and some brain dead hardware engineers forgot to make the state of that switch readable to the PC doing the programming...
That sounds like the hardware engineer was working under a different set of assumptions to you. So while the lack of a read/write status indicator sounds pretty stupid to me, I'm thinking that the difference of opinion is the bigger issue here.
-
@Anonymouse said:
you're usually not in the position to refuse doing that and demand a redesign of the hardware to be made
No.. you're not.. but you are in the ideal position to suggest design modifications to prevent said defects occuring in the first place, or at the very least some modifications that could speed up the diagnosis and fix process.
Whether or not those ideas are welcommed, accepted and implemented are another matter.
-
@Anonymouse said:
Admittedly, that was 2008, not 2012, but either way, if you're the unlucky bloke who gets a bunch of badly designed devices dumped on his desk and is told to make them f-ing work, you're usually not in the position to refuse doing that and demand a redesign of the hardware to be made, just because otherwise it would require you to violate your ideas of proper UI design to get it done...
I'd quit then.
