> While I agree with you that it is a didactic problem, I also think it is an optimisation heuristic. When working with engineers, it is expected that they know what, for example, git/version control is, hence such jargon will be sprinkled in conversation freely. That's how we compress the communication bandwidth. It is enormously costly if we document everything in a context free manner that anyone newly into the topic can understand, and people still won't understand.
This is exactly the reason I ask some common knowledge jargon during interviews.
I start by saying, "hey, I know this is silly but I'm going to ask you some basic questions, please explain to me what you think it means.. JSON, REST..."
You'd be shocked how many strange / ridiculous answers I get, along with a few that after 10 words I know I'm speaking with someone that has a change getting the position.
This is part of an initial 30 minute phone interview.
This is exactly the reason I ask some common knowledge jargon during interviews. I start by saying, "hey, I know this is silly but I'm going to ask you some basic questions, please explain to me what you think it means.. JSON, REST..." You'd be shocked how many strange / ridiculous answers I get, along with a few that after 10 words I know I'm speaking with someone that has a change getting the position. This is part of an initial 30 minute phone interview.