You may be a very technical person. However, the listener may not. Do not describe your problems employing any technical jargon that the listener does not know or understand.Note that this may involve (gasp!) asking them if they're still following the discussion. Drives me bonkers when I'm talking to someone and they start out making sense, then continue on into Never Never Land of Technical Issues. I don't mind technical issues at all but I don't know everything. Just because I understand object-oriented design doesn't mean I know how a TTP bus works. (No, no relation between the two AFAIK, but this was a recent issue -- the person giving me info was surprised that I knew one but not the other)
And if you're communicating using the written word, double check things before you send it off. Just like Previewing on PM.
In reply to Re: Programming skill #1: Communication
by Nkuvu
in thread Programming skill #1: Communication
by Tanktalus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |