Timeline for Constructively dealing with people using jargon incorrectly/misleadingly
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23, 2016 at 0:40 | comment | added | Brandin | @paj28 You don't have to copy their terminology. I think the point of this answer is that if you shouldn't step in unnecessarily to correct someone when it doesn't matter too much. "Wait, did you say one way encryption? That terminology is so wrong and if you use it you risk sounding ignorant. You should actually say it like this..." (ok, you probably wouldn't phrase it like this, but if you're too pushy it may come across something like that to the other party). But at the end of the day just use whatever term you normally use. | |
| Oct 22, 2016 at 17:46 | comment | added | paj28 | I like it :) That was a simplified example; in a real world scenario, I'd need to provide additional info like "make sure to use a strong hashing algorithm" and "use a salt with the hash". So I would need to choose one approach or the other, but hey, maybe that depends entirely on the context. | |
| Oct 22, 2016 at 17:28 | comment | added | paj28 | Good edit. I agree completely, correct when it matters. One follow-up question: should I use the other person's slightly incorrect terminology, or the correct one? e.g. "We're going to store passwords with one way encryption, that ok?". I can answer "Sure, one way encryption is good" or "Sure, hashing is good". | |
| Oct 22, 2016 at 15:17 | history | edited | Joe Strazzere | CC BY-SA 3.0 |
added 102 characters in body
|
| Oct 22, 2016 at 15:01 | comment | added | AllTheKingsHorses | @paj28 I see a greater risk for you than people thinking "plaintext passwords are ok" because you said "plaintext passwords sent over HTTPS are ok": the risk that people start ignoring you because they feel you are a pedantic nitpicker who needs to put others down by "enforcing" terminology you consider correct even though you perfectly understood them the first time. I've had colleagues like that in the past and seen work relationships implode because of it. It can get really unproductive. On the other hand none of the examples in your OP would strike me as particularly problematic. | |
| Oct 22, 2016 at 12:57 | comment | added | paj28 | I absolutely do see the difference of "when it matters". Your answer implies you should not correct in conversations. I guess you meant "only correct when it matters". If you edit your answer to make that clear, I will upvote. BTW, my job is not formally in educating people, but I think that most professional jobs - and certainly mine - have an informal role of educating colleagues. | |
| Oct 22, 2016 at 12:21 | comment | added | paj28 | I worry about future misinterpretation. e.g. I say "plaintext passwords over HTTPS is ok". They later say "you said plaintext passwords are ok". I guess I can always challenge the later interpretation. But enforcing proper use of terminology would avoid a number of these misunderstandings. | |
| Oct 22, 2016 at 12:12 | comment | added | paj28 | Could be a hallway conversation, phone call, or something more formal, e.g. a design committee. | |
| Oct 22, 2016 at 12:08 | comment | added | paj28 | Thanks for the answer. Correcting others in conversation might be considered rude, I agree - but what if it's a correction that really matters? | |
| Oct 22, 2016 at 11:57 | history | answered | Joe Strazzere | CC BY-SA 3.0 |