4 ms·
Depends on the role. For example, I think a postman is a government employee? In that case, about the same as I'd think of an Amazon engineer who didn't know th
by philh 11y ago
Depends on the role. For example, I think a postman is a government employee? In that case, about the same as I'd think of an Amazon engineer who didn't know that. I have no idea how they don't know it, and I think a little less of them for it. But if it's not relevant for their work, I don't judge their skill by it, and I don't think less of them than I do of anyone else.
If you want me to be - offended? shocked? contemptuous? - of what someone doesn't know, please tell me why it's so important for them to know it. Not just why it could potentially be useful for someone in their role. Why it's so important for anyone in this role, that this particular thing gets singled out, suggests in lieu of all other data that they're incompetent.
I'm an engineer at a publicly traded company. (Or so I assume. I could be mistaken.) I can think of dozens of things I don't know that would be useful for me to know. I do know what a publicly traded company is, but this knowledge is not useful for me in my role.
- throwawaymsft 11y agoWould you want to work with someone who "is sure" of a trivially verifiable fact? It's ok to be ignorant ("I have no idea who owns what") but to be sure of something that pants-on-head false? What else are they "sure" about?