Worked with a guy recently who emailed me with "I don't understand arrays". I immediately called him and said "we've got some big problems - this is scaring me

Worked with a guy recently who emailed me with "I don't understand arrays". I immediately called him and said "we've got some big problems - this is scaring me, that you'd write that - you need to understand arrays." I got back "oh, I understand arrays - I don't understand why what they're used for." Me: "Holy cow - how can you understand array but not know what they're used for? That doesn't make sense." Him: "No, I mean I don't know why this framework uses them in these 2 libraries." Me: "Please learn to communicate your full thought before emailing me. This seriously makes me question your ability to get any of this done - you're not able to get your thoughts across properly - how can I assume you can understand what I'm saying, what the requirements are, or translate to code correctly? You might be able to, but you lose credibility when you write and talk this loosely - words have meaning." "I don't understand why the framework uses arrays in supporting library X" is miles different from "I don't understand arrays". But in his mind, he was saying the same thing.