Customer-facing identifiers

I’m still installing miscellaneous drivers for my work laptop (Dell Inspiron 1501).  I just downloaded an additional printer driver for an office printer, but can anyone tell me in less than 5 seconds, without Googling, which file is the printer driver?

Unless you have Internet access, you’ll have a tough time guessing which is which.  That doesn’t really help me when one of the drivers I’m installing is the network driver, and therefore have no Internet access yet.

I think this is a prime example of technical data making its way to the customer’s eyes, when it shouldn’t.  Nothing on these files gives any indication what the driver is for.  I understand needing to have some identifying values on the file name for support purposes, but can I at least get a category in the file name? At least twice I’ve clicked and guessed wrong this week.

I was on a product team once that used GUIDs for all entity identifiers.  Unfortunately, we also forced the users to use the GUIDs to load any entity from our API, but provided no way to easily extract them from any user interface.  End users had to manually type in all 32 hexadecimal characters from going back and forth from the screen to the code.  The irate emails cascaded down, and we didn’t make that mistake again.

Customers care about identity, they want to know that they’re retrieving the right customer, and that the customer they’re retrieving isn’t duplicated.  Developers sometimes make the mistake that customers always care about how the identity is maintained, through a GUID or otherwise.  Under most circumstances, they don’t, so we shouldn’t force our special internal technical solutions for identities on customers and end users.  It’s one of the quickest ways to confuse them.

Advanced CI: integrating web applications